Hi, I want to give an update for this. I also tested READ speed. It seems, sharded volume has a lower read speed than striped volume. This machine has 24 cores with 64GB of RAM . I really don’t think its caused due to low system. Stripe is kind of a shard but a fixed size based on stripe value / filesize. Hence, I would expect at least the same speed or maybe little slower. What I get is 5-10x slower. I play with Gluster’s threads count, performance tweaks, caches and etc. Nothing helped. In fact, the performance tweaks that I apply for stripe makes sharded volume much much more worse. Default values are better on sharded volume. -Gencer. From: gencer@xxxxxxxxxxxxx [mailto:gencer@xxxxxxxxxxxxx] I did the changes (one brick from 09th server and one replica from 10th server and continued with this order) and re-test. Nothing changed. Still slow. (exactly same result.) -Gencer. From: Gandalf Corvotempesta [mailto:gandalf.corvotempesta@xxxxxxxxx] Il 30 giu 2017 3:51 PM, <gencer@xxxxxxxxxxxxx> ha scritto:
Yes, you have to specify the exact order Gluster is not flexible in this way and doesn't help you at all. |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
