[Gluster-users] Tiering and sharding for VM workload

Krutika Dhananjay kdhananj at redhat.com
Tue Sep 6 13:08:21 UTC 2016


Theoretically whatever you said is correct (at least from shard's
perspective).
Adding Rafi who's worked on tiering to know if he thinks otherwise.

It must be mentioned that sharding + tiering hasn't been tested as such
till now by us at least.

Did you try it? If so, what was your experience?

-Krutika

On Tue, Sep 6, 2016 at 5:59 PM, Gandalf Corvotempesta <
gandalf.corvotempesta at gmail.com> wrote:

> 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?
>>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160906/c421c076/attachment.html>


More information about the Gluster-users mailing list