search for: synctest

...ork OK - brief usage details are at the web site. The intent here is that the external journal be an NVRAM device (or a disk) which can be used to accelerate full-data journalling. Simulation using a normal RAM drive indicates that we can double throughput with some loads (dbench) but not others (synctest). More work is needed to fully characterise this. For the synchronous operations I've put together an application which attempts to simulate an MTA's behaviour. The simulator is called `synctest' and it is in ext3 CVS. There's a copy at http://www.uow.edu.au/~andrewm/synctest.c...

Dear Wayne, I am using rsync to synchronize my working files from home computer to the work computer. I want to sync only the files in some directories and no .files. However, I do need to sync several files from .mozilla director (addressbook, calendar and bookmarks) which are located in the .directory. I use the following command and the "excluded-utk.txt" file rsync -aunvz

...does not seem to make any difference. 2) Where is the bottleneck exactly? I currently have this setup in my smb.conf, just listing the lines I edited (the rest is default): [global] netbios name = prox case sensitive = no server min protocol = SMB3 client min protocol = SMB3 [Media] path = /zfs/synctest valid users = myuser read only = no writeable = yes guest ok = no create mode = 770 directory mode = 770 syncops:disable = true # I tried the test with both this option enabled as well as commented out, and it didn't seem to make a difference. Thanks in advance.

I''ve been working to try to improve the write-ahead log''s performance, and I found that the bottleneck addresses in the checksum items, especially when we want to make a random write on a large file, e.g a 4G file. Then a idea for this suggested by Chris is to use sub transaction ids and just to log the part of inode that had changed since either the last log commit or the last

...bottleneck exactly? > > I currently have this setup in my smb.conf, just listing the lines I edited (the rest is default): > > [global] > netbios name = prox > case sensitive = no > server min protocol = SMB3 > client min protocol = SMB3 > > [Media] > path = /zfs/synctest > valid users = myuser > read only = no > writeable = yes > guest ok = no > create mode = 770 > directory mode = 770 > syncops:disable = true # I tried the test with both this option enabled as well as commented out, and it didn't seem to make a difference. syncops paramet...

...t; > I currently have this setup in my smb.conf, just listing the lines I edited (the rest is default): > > [global] > > netbios name = prox > > case sensitive = no > > server min protocol = SMB3 > > client min protocol = SMB3 > > [Media] > > path = /zfs/synctest > > valid users = myuser > > read only = no > > writeable = yes > > guest ok = no > > create mode = 770 > > directory mode = 770 > > syncops:disable = true # I tried the test with both this option enabled as well as commented out, and it didn't seem to...