From: "Adam Kropelin" <akropel1@rochester.rr.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Writeout in recent kernels/VMs poor compared to last -ac
Date: Sat, 12 Jan 2002 13:19:41 -0500 [thread overview]
Message-ID: <00fd01c19b95$b3ec3a40$02c8a8c0@kroptech.com> (raw)
In-Reply-To: <009e01c19b7c$463457d0$02c8a8c0@kroptech.com> <20020112173018.Q1482@inspiron.school.suse.de>
----- Original Message -----
From: "Andrea Arcangeli" <andrea@suse.de>
To: "Adam Kropelin" <akropel1@rochester.rr.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Saturday, January 12, 2002 11:30 AM
Subject: Re: Writeout in recent kernels/VMs poor compared to last -ac
> On Sat, Jan 12, 2002 at 10:17:39AM -0500, Adam Kropelin wrote:
> > I recently began regularly transferring large (600 MB+) files to my
> > Linux-based fileserver and have noticed what I would characterize as poor
> > writeout behavior under this load. I've done a bit of comparison testing
> > which may help reveal the problem better.
<snip>
> I think you simply want to trigger the soft-bdflush event earlier, with
> -aa something like this may do the trick:
>
> echo 5 500 64 256 500 3000 60 2 0 > /proc/sys/vm/bdflush
>
> this way you'll wakeup as soon as 5% of the 118mbytes (+ free memory,
> none in this case) are dirty, and bdflush will stop as soon as the level
> is back to 2% (then kupdate will take care of the 2%). Those suggested
> values may be too strict but this way you should get the idea if it
> helps somehow or not :)
Thanks for the idea. Unfortunately, it didn't help. :(
Blocks definitely do begin hitting the disk much sooner after I begin the
transfer, but the overall time is basically unchanged: 7:08. vmstat still shows
the widely oscillating bo value.
--Adam
next prev parent reply other threads:[~2002-01-12 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 15:17 Adam Kropelin
2002-01-12 15:29 ` Adam Kropelin
2002-01-12 16:03 ` Rik van Riel
2002-01-12 16:30 ` Andrea Arcangeli
2002-01-12 18:19 ` Adam Kropelin [this message]
2002-01-12 18:49 ` Jussi Laako
2002-01-12 20:47 ` Jeff Lessem
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00fd01c19b95$b3ec3a40$02c8a8c0@kroptech.com' \
--to=akropel1@rochester.rr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®