Speed of glusterfs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 14.12.2011 14:54, schrieb Marc Muehlfeld:
> Am 14.12.2011 14:00, schrieb Rapha?l Hoareau:
>> You could also try to use two NICs with specific routes. NIC1 knows the
>> route to Server1 and NIC2 knows the route to Server2.
>
> Could it be possible that this can't be done or do I miss something?

(For my speed test results see the end of this mail)



I saw what was wrong: When I

# gluster peer probe ...

from one node to the other, then glusterfs automatically allows it's own IP 
from *the same subnet*.


If I probe both server from a client and then it works:

# gluster peer probe 192.168.20.14
Probe successful

# gluster peer probe 192.168.29.15
Probe successful

# gluster volume create test replica 2 transport tcp 192.168.20.14:/mnt/ 
192.168.29.15:/mnt/
Creation of volume test has been successful. ...


Netstat also shows that the client is connected to both nodes with each on a 
own IP in a separare subnet (and NIC):

# netstat -taunp | grep glusterfs
tcp        0      0 192.168.29.1:1022           192.168.29.15:24011 
VERBUNDEN   23488/glusterfs
tcp        0      0 192.168.20.1:1019           192.168.20.14:24011 
VERBUNDEN   23310/glusterfs
....





Here are the results:

Im writing a 10 GB file to the cluster:

time dd if=/dev/zero of=/mnt/test.10G bs=1M count=10000
10000+0 Datens?tze ein
10000+0 Datens?tze aus
10485760000 Bytes (10 GB) kopiert, 106,981 s, 98,0 MB/s

real    1m47.018s
user    0m0.010s
sys     0m5.801s

This is a good result for me on a 1GBit connection.


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux