similar to: Helping OS's page cache

On Fri, Aug 7, 2020, 16:16 Richard W.M. Jones <rjones@redhat.com> wrote: > On Fri, Aug 07, 2020 at 07:53:13AM -0500, Eric Blake wrote: > > >$ free -m; time ./nbdkit file /var/tmp/random fadvise=sequential > cache=none --run 'qemu-img convert -n -p -m 16 -W $nbd >

On 8/7/20 6:31 AM, Richard W.M. Jones wrote: > You can use these flags as described in the manual page to optimize > access patterns, and to get better behaviour with the page cache in > some scenarios. And if you guess wrong, it is only a performance penalty, not a correctness issue. > > For my testing I used the cachedel and cachestats utilities written by > Julius Plenz

On Sat, Aug 08, 2020 at 01:24:02AM +0300, Nir Soffer wrote: > The new cache=none mode is misleading since it does not avoid usage of > the page cache. When using shared storage, we may get stale data from > the page cache. When writing, we flush after every write which is > inefficient and unneeded. > Hmm. This isn't actually what the cache=none parameter is currently doing.

v1.1 plans have changed a bit. I'll release v1.1.alpha1 soon and hope to have a stable v1.1 in a month or two. The rest of the features that didn't make it into v1.1 will go to v1.2. I'll write more about this when v1.1 alpha is released. I also did a bit of benchmarking. v1.1's performance improvements are looking pretty great, it seems to be twice as fast as v1.0. v1.0:

Hi List, I have updated my rsync fadvise patch which stops rsync from ousting all your other data from cache when running large jobs. I have also written an article about the whole issue. http://insights.oetiker.ch/linux/fadvise.html cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten http://it.oetiker.ch tobi@oetiker.ch ++41 62 213 9902

On Fri, Aug 07, 2020 at 07:53:13AM -0500, Eric Blake wrote: > >$ free -m; time ./nbdkit file /var/tmp/random fadvise=sequential cache=none --run 'qemu-img convert -n -p -m 16 -W $nbd "json:{\"file.driver\":\"null-co\",\"file.size\":\"1E\"}"' ; free -m ; cachestats /var/tmp/random > > Hmm - the -W actually says that qemu-img is

You can use these flags as described in the manual page to optimize access patterns, and to get better behaviour with the page cache in some scenarios. For my testing I used the cachedel and cachestats utilities written by Julius Plenz (https://github.com/Feh/nocache). I started with a 32 GB file of random data on a machine with about 32 GB of RAM. At the beginning of the test I evicted the

On Sun, Aug 9, 2020 at 12:28 AM Richard W.M. Jones <rjones@redhat.com> wrote: > > On Sat, Aug 08, 2020 at 01:24:02AM +0300, Nir Soffer wrote: > > The new cache=none mode is misleading since it does not avoid usage of > > the page cache. When using shared storage, we may get stale data from > > the page cache. When writing, we flush after every write which is > >

The new cache=none mode is misleading since it does not avoid usage of the page cache. When using shared storage, we may get stale data from the page cache. When writing, we flush after every write which is inefficient and unneeded. Rename the cache modes to: - writeback - write complete when the system call returned, and the data was copied to the page cache. - writethrough - write completes

Webmail.us will be sponsoring my Dovecot development for this summer. Other companies are also welcome to participate in the costs. Participation gets you: - listed in Credits in www.dovecot.org - listed in AUTHORS file - you can tell me how you want to use the feature and I'll make sure that it supports it (within reasonable limits) For already implemented v1.1 features, see

http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig Two hours later than promised, I slept longer than intended. :) No changes since v1.1.rc13. Below are the largest changes since v1.0: * After Dovecot v1.1 has modified index or dovecot-uidlist files, they can't be opened anymore with Dovecot versions earlier than v1.0.2. *

http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.0.tar.gz.sig Two hours later than promised, I slept longer than intended. :) No changes since v1.1.rc13. Below are the largest changes since v1.0: * After Dovecot v1.1 has modified index or dovecot-uidlist files, they can't be opened anymore with Dovecot versions earlier than v1.0.2. *

On 25 Feb 2017, at 21.54, Timo Sirainen <tss at iki.fi> wrote: > > Oh, I forgot to remove the #if OPENSSL_VERSION_NUMBER checks from lib-dcrypt. Will be removed in v2.2.29. Attached the planned patch that should do it. Well that didn't work with <v1.1. Maybe this one. -------------- next part -------------- A non-text attachment was scrubbed... Name: openssl.diff Type:

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post. This is the only v1.1.alpha announcement I send

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post. This is the only v1.1.alpha announcement I send

https://bugzilla.samba.org/show_bug.cgi?id=9560 Summary: drop-cache option Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: colundrum at gmail.com QAContact: rsync-qa at

Hi, I can see this has been discussed previously, was just wondering if it's been fixed in v1.1.x? -- Best Regards, Stephen

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta15.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta15.tar.gz.sig It's been a while since the previous beta, so I guess it's time for a new release. I wanted this one to be called v1.1.rc1, but Squat indexes still aren't completely working. My simple tests seem to work OK, but after doing some random

On 12/2/2007, Timo Sirainen (tss at iki.fi) wrote: > On Sun, 2007-12-02 at 10:02 -0500, Charles Marcus wrote: >> Do you have any idea as to a time frame for when you might be able >> to get to it (Single instance Storage)? Are you thinking post >> v2.0? Even 2.1 or 3.0? > Right now I just want to get v1.1 finished. The main problem with it > is that apparently in

On Sat, Aug 19, 2017 at 4:27 PM, Csaba Henk <chenk at redhat.com> wrote: > Hi Niels, > > On Fri, Aug 11, 2017 at 2:33 PM, Niels de Vos <ndevos at redhat.com> wrote: > > On Fri, Aug 11, 2017 at 05:50:47PM +0530, Ravishankar N wrote: > [...] > >> To me it looks like fadvise (mm/fadvise.c) affects only the linux page > cache > >> behavior and is