It was simple emulation of network packets on the port of the server node using tc tool tc qdisc add dev <port> root netem delay <time>ms. The files were created using dd tool (in-built in linux) and mkdir. Post the IO's we verified with no pending heals.
Thanks & Regards
On Thu, Sep 28, 2017 at 2:06 PM, Arman Khalatyan <arm2arm@xxxxxxxxx> wrote:
thanksInteresting table Karan!,Could you please tell us how you did the benchmark? fio or iozone orsimilar?
Arman.On Wed, Sep 27, 2017 at 1:20 PM, Karan Sandha <ksandha@xxxxxxxxxx> wrote:Hi Collin,During our arbiter latency testing for completion of ops we found the below results:- an arbiter node in another data centre and both the data bricks in the same data centre,1) File-size 1 KB (10000 files )2) mkdir
Latency
5ms
10ms
20ms
50ms
100ms
200ms
Ops
Create
755 secs
1410 secs
2717 secs
5874 secs
12908 sec
26113 sec
Mkdir
922 secs
1725 secs
3325 secs
8127 secs
16160 sec
30079 sec
Thanks & RegardsOn Mon, Sep 25, 2017 at 5:40 AM, Colin Coe <colin.coe@xxxxxxxxx> wrote:______________________________Hi allI've googled but can't find an answer to my question.I have two data centers. Currently, I have a replica (count of 2 plus arbiter) in one data center but is used by both.I want to change this to be a distributed replica across the two data centers.There is a 20Mbps pipe and approx 22 ms latency. Is this sufficient?I really don't want to do the geo-replication in its current form.ThanksCC_________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users --
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
