search for: nostrictsync

...mnt type cifs (rw,relatime,vers=3.1.1,sec=none,cache=strict,uid=0,noforceuid,gid=0,noforcegid,addr=127.0.0.1,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) root at plattentest:~# mounting the share with cache=loose, nostrictsync and noblocksend adds another minute, adding "aio write behind = *" to the share definition does next to nothing. neither cpu nor ram are bottlenecks. thank you very much & with kind regards, t. -------------- next part -------------- A non-text attachment was scrubbed... Name: signa...

...454.345 454.345 0.000 Tree creation : 314.333 314.333 314.333 0.000 Tree removal : 382.234 382.234 382.234 0.000 -- finished at 02/17/2023 10:26:28 -- Additionally, it seems our client does not have any kind of cache available. I've tried many options: - cache=loose - actimeo=3600 - nostrictsync - noperm - fsc - etc.... But none of the seems to have an impact. Our work load consists of mainly large number of small files. I know there many possible factors going on here. So I'm wondering if there is any way we could profile/trace this to tune the performance. Thanks! Info...

...rw,relatime,vers=3.1.1,sec=none,cache=strict,uid=0,noforceuid,gid=0,noforcegid,addr=127.0.0.1,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) > root at plattentest:~# > > mounting the share with cache=loose, nostrictsync and noblocksend adds > another minute, adding "aio write behind = *" to the share definition > does next to nothing. neither cpu nor ram are bottlenecks. This is re-exporting via ceph whilst creating 1000 files, yes ? What timings do you get when doing this via Samba onto a local e...

...314.333 314.333 314.333 0.000 Tree removal : 382.234 > 382.234 382.234 0.000 -- finished at 02/17/2023 10:26:28 -- > > Additionally, it seems our client does not have any kind of cache > available. I've tried many options: > > - cache=loose > - actimeo=3600 > - nostrictsync > - noperm > - fsc > - etc.... > > But none of the seems to have an impact. > > Our work load consists of mainly large number of small files. > > I know there many possible factors going on here. So I'm wondering if > there is any way we could profile/trac...

hi there, running a simple test like time for s in $(seq 0 9999); do echo hello > world-$s; done takes a little more than a minute on a locally mounted test share on our samba server. the same test finishes in about 5 seconds when it is run on the server's file system, without samba. i understand that dealing with many small files isn't exactly the sweet spot of any (networked) file