Gluster users - Sep 2016 - Tiering and sharding for VM workload

Is tiering with sharding usefull with VM workload?
Let's assume a storage with tiering and sharding enabled, used for
hosting VM images.
Each shard is subject to tiering, thus the most frequent part of the
VM would be cached on the SSD, allowing better performance.

Is this correct?

To put it simple, very simple, let's assume a webserver VM, with the
following directory structure:

/home/user1/public_html
/home/user2/public_html

both are stored on 2 different shards (i'm semplyfing).
/home/user1/public_html has much more visits than user2.

Would that shard cached on hot tier allowing faster access by the webserver?

Anybody?

Il 05 set 2016 22:19, "Gandalf Corvotempesta" <
gandalf.corvotempesta at gmail.com> ha scritto:
> Is tiering with sharding usefull with VM workload?
> Let's assume a storage with tiering and sharding enabled, used for
> hosting VM images.
> Each shard is subject to tiering, thus the most frequent part of the
> VM would be cached on the SSD, allowing better performance.
>
> Is this correct?
>
> To put it simple, very simple, let's assume a webserver VM, with the
> following directory structure:
>
> /home/user1/public_html
> /home/user2/public_html
>
> both are stored on 2 different shards (i'm semplyfing).
> /home/user1/public_html has much more visits than user2.
>
> Would that shard cached on hot tier allowing faster access by the
> webserver?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160906/23991d07/attachment.html>