search for: smallfile_c

...? ? I just did a mount like this (added the bold): ? mount -t glusterfs -o attribute-timeout=600,entry-timeout=600,negative-timeout=600,fopen-keep-cache,use-readdirp=no,log-level=WARNING,log-file=/var/log/glusterxxx.log 192.168.140.41:/www /var/www ?Results: ? root at app1:~/smallfile-master# ./smallfile_cli.py ?--top /var/www/test --host-set 192.168.140.41 --threads 8 --files 5000 --file-size 64 --record-size 64 smallfile version 3.0 ? ? ? ? ? ? ? ? ? ? ? ? ? ?hosts in test : ['192.168.140.41'] ? ? ? ? ? ? ? ? ? ?top test directory(s) : ['/var/www/test'] ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?...

...? ? I just did a mount like this (added the bold): ? mount -t glusterfs -o attribute-timeout=600,entry-timeout=600,negative-timeout=600,fopen-keep-cache,use-readdirp=no,log-level=WARNING,log-file=/var/log/glusterxxx.log 192.168.140.41:/www /var/www ?Results: ? root at app1:~/smallfile-master# ./smallfile_cli.py ?--top /var/www/test --host-set 192.168.140.41 --threads 8 --files 5000 --file-size 64 --record-size 64 smallfile version 3.0 ? ? ? ? ? ? ? ? ? ? ? ? ? ?hosts in test : ['192.168.140.41'] ? ? ? ? ? ? ? ? ? ?top test directory(s) : ['/var/www/test'] ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?...

...; > > mount -t glusterfs -o > *attribute-timeout=600,entry-timeout=600,negative-timeout=600,fopen-keep-cache* > ,use-readdirp=no,log-level=WARNING,log-file=/var/log/glusterxxx.log > 192.168.140.41:/www /var/www > > > Results: > > > root at app1:~/smallfile-master# ./smallfile_cli.py --top /var/www/test > --host-set 192.168.140.41 --threads 8 --files 5000 --file-size 64 > --record-size 64 > smallfile version 3.0 > hosts in test : ['192.168.140.41'] > top test directory(s) : ['/var/www/test'] >...

...gluster 3.10, there are no other differences, except glusterfs versus nfs. The nfs is about 80 times faster: ? ? root at app1:~/smallfile-master# mount -t glusterfs -o use-readdirp=no,log-level=WARNING,log-file=/var/log/glusterxxx.log 192.168.140.41:/www /var/www root at app1:~/smallfile-master# ./smallfile_cli.py ?--top /var/www/test --host-set 192.168.140.41 --threads 8 --files 500 --file-size 64 --record-size 64 smallfile version 3.0 ? ? ? ? ? ? ? ? ? ? ? ? ? ?hosts in test : ['192.168.140.41'] ? ? ? ? ? ? ? ? ? ?top test directory(s) : ['/var/www/test'] ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?...

...luster.quorum-type: auto ?I started with none of them set and I added/changed while testing. But it was always slow, by tuning some kernel parameters it improved slightly (just a few percent, nothing reasonable) ?I also tried ceph just to compare, I got this with default settings and no tweaks: ??./smallfile_cli.py ?--top /var/www/test --host-set 192.168.140.41 --threads 8 --files 5000 --file-size 64 --record-size 64 smallfile version 3.0 ? ? ? ? ? ? ? ? ? ? ? ? ? ?hosts in test : ['192.168.140.41'] ? ? ? ? ? ? ? ? ? ?top test directory(s) : ['/var/www/test'] ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?...

...t; > > > After that I tried nfs (native gluster nfs 3 and ganesha nfs 4), it was > a crazy performance difference. > > > > e.g.: 192.168.140.41:/www /var/www nfs4 defaults,_netdev 0 0 > > > > I tried a test like this to confirm the slowness: > > > > ./smallfile_cli.py ?--top /var/www/test --host-set 192.168.140.41 > --threads 8 --files 5000 --file-size 64 --record-size 64 > > This test finished in around 1.5 seconds with NFS and in more than 250 > seconds without nfs (can't remember exact numbers, but I reproduced it > several times for b...

...m-type: auto ? I started with none of them set and I added/changed while testing. But it was always slow, by tuning some kernel parameters it improved slightly (just a few percent, nothing reasonable) ? I also tried ceph just to compare, I got this with default settings and no tweaks: ? ?./smallfile_cli.py ?--top /var/www/test --host-set 192.168.140.41 --threads 8 --files 5000 --file-size 64 --record-size 64 smallfile version 3.0 ? ? ? ? ? ? ? ? ? ? ? ? ? ?hosts in test : ['192.168.140.41'] ? ? ? ? ? ? ? ? ? ?top test directory(s) : ['/var/www/test'] ? ? ? ? ? ? ? ? ? ? ?...

...added/changed while >> testing. But it was always slow, by tuning some kernel parameters >> it improved slightly (just a few percent, nothing reasonable) >> I also tried ceph just to compare, I got this with default >> settings and no tweaks: >> ./smallfile_cli.py --top /var/www/test --host-set >> 192.168.140.41 --threads 8 --files 5000 --file-size 64 >> --record-size 64 >> smallfile version 3.0 >> hosts in test : ['192.168.140.41'] >> top test direc...

...I started with none of them set and I added/changed while testing. But > it was always slow, by tuning some kernel parameters it improved > slightly (just a few percent, nothing reasonable) > I also tried ceph just to compare, I got this with default settings > and no tweaks: > ./smallfile_cli.py --top /var/www/test --host-set 192.168.140.41 > --threads 8 --files 5000 --file-size 64 --record-size 64 > smallfile version 3.0 > hosts in test : ['192.168.140.41'] > top test directory(s) : ['/var/www/test'] >...

...timeout=1,use-readdirp=no,log-level=WARNING,log-file=/var/log/glusterxxx.log 192.168.140.41:/www /var/www ?mount -t glusterfs -o use-readdirp=no,log-level=WARNING,log-file=/var/log/glusterxxx.log 192.168.140.41:/www /var/www ?So it means only 1 second negative timeout... ?In this particular test:?./smallfile_cli.py ?--top /var/www/test --host-set 192.168.140.41 --threads 8 --files 50000 --file-size 64 --record-size 64 ??The result is about 4 seconds with the negative timeout of 1 second defined and many many minutes without the negative timeout (I quit after 15 minutes of waiting) ?I will go over to som...

...tried some mount variants in order to speed up things without luck. ? ? After that I tried nfs (native gluster nfs 3 and ganesha nfs 4), it was a crazy performance difference. ? e.g.:?192.168.140.41:/www /var/www nfs4 defaults,_netdev 0 0 ? I tried a test like this to confirm the slowness: ? ./smallfile_cli.py ?--top /var/www/test --host-set 192.168.140.41 --threads 8 --files 5000 --file-size 64 --record-size 64 ?This test finished in around 1.5 seconds with NFS and in more than 250 seconds without nfs (can't remember exact numbers, but I reproduced it several times for both). ?With the native g...

...rbiter) Options Reconfigured: features.quota-deem-statfs: on nfs.disable: on features.inode-quota: on features.quota: on And I ran the smallfile benchmark, created 80k 64KB files. After that I clear cache everywhere and ran a smallfile stat test [root at dell-per730-06-priv ~]# python /smallfile/smallfile_cli.py --files 10000 --file-size 64 --threads 8 --top /gluster-mount/s-file/ --operation stat version : 3.1 hosts in test : None top test directory(s) : ['/gluster-mount/s-file'] oper...

...t; > > > After that I tried nfs (native gluster nfs 3 and ganesha nfs 4), it was > a crazy performance difference. > > > > e.g.: 192.168.140.41:/www /var/www nfs4 defaults,_netdev 0 0 > > > > I tried a test like this to confirm the slowness: > > > > ./smallfile_cli.py --top /var/www/test --host-set 192.168.140.41 > --threads 8 --files 5000 --file-size 64 --record-size 64 > > This test finished in around 1.5 seconds with NFS and in more than 250 > seconds without nfs (can't remember exact numbers, but I reproduced it > several times for b...

Hi, I have a gluster 3.10 volume with a dir with ~1 million small files in them, say mounted at /mnt/dir with FUSE, and I'm observing something weird: When I list and stat them all using rsync, then the lstat() calls that rsync does are incredibly fast (23 microseconds per call on average, definitely faster than a network roundtrip between my 3-machine bricks connected via Ethernet). But