Re: Tiering and sharding for VM workload

[Mohammed Rafi K C <rkavunga@xxxxxxxxxx>]

Yes, you are correct. On a sharded volume, the hot and cold would be based on sharded chunks.

I'm stressing the point which Krutika mentioned in her mail that we haven't tested the use case in depth.

Regards
Rafi KC

On 09/06/2016 06:38 PM, Krutika Dhananjay wrote:

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@xxxxxxxxx> wrote:

Anybody?

Il 05 set 2016 22:19, "Gandalf Corvotempesta" <gandalf.corvotempesta@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@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users