Linux NFS development
 help / color / mirror / Atom feed
From: Jos Houtman <jos@hyves.nl>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	<linux-kernel@vger.kernel.org>, Jeff Layton <jlayton@redhat.com>,
	Dave Chinner <david@fromorbit.com>,
	<linux-fsdevel@vger.kernel.org>, <jens.axboe@oracle.com>,
	<akpm@linux-foundation.org>, <hch@infradead.org>,
	<linux-nfs@vger.kernel.org>
Subject: Re: Page Cache writeback too slow,   SSD/noop scheduler/ext2
Date: Mon, 30 Mar 2009 17:47:19 +0100	[thread overview]
Message-ID: <C5F6B627.D9D0%jos@hyves.nl> (raw)
In-Reply-To: <20090329023238.GA7825@localhost>


>> Thanx for the patch, but for the next time: How should I apply it?
>> it seems to be context aware (@@) and broke on all kernel versions I tried
>> 2.6.28/2.6.28.7/2.6.29
> 
> Do you mean that the patch applies after removing " @@.*$"?

I didn't try that, but this time it worked. So it was probably my error.

> 
> You are right. In your case, there are several big dirty files in sdb1,
> and the sdb write queue is constantly (almost-)congested. The SSD write
> speed is so slow, that in each round of sdb1 writeback, it begins with
> an uncongested queue, but quickly fills up after writing some pages.
> Hence all the inodes will get redirtied because of (nr_to_write > 0).
> 
> The following quick fix should solve the slow-writeback-on-congested-SSD
> problem. However the writeback sequence is suboptimal: it sync-and-requeue
> each file until congested (in your case about 3~600 pages) instead of
> until MAX_WRITEBACK_PAGES=1024 pages.

Yeah that fixed it, but performance dropped due to the more constant
congestion. So I will need to try some different io schedulers.


Next to that I was wondering if there are any plans to make sure that not
all dirty-files are written back in the same interval.

In my case all database files are written back each 30 seconds, while I
would prefer them to be more divided over the interval.

Thanks,

Jos


  reply	other threads:[~2009-03-30 15:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C5EC2B99.C3B3%jos@hyves.nl>
     [not found] ` <200903250148.53644.nickpiggin@yahoo.com.au>
2009-03-25  5:26   ` Page Cache writeback too slow, SSD/noop scheduler/ext2 Wu Fengguang
2009-03-27 16:59     ` Jos Houtman
2009-03-29  2:32       ` Wu Fengguang
2009-03-30 16:47         ` Jos Houtman [this message]
2009-03-31  0:28           ` Wu Fengguang
2009-03-31 12:16           ` Jos Houtman
2009-03-31 12:31             ` Wu Fengguang
2009-03-31 14:10               ` Jos Houtman

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=C5F6B627.D9D0%jos@hyves.nl \
    --to=jos@hyves.nl \
    --cc=akpm@linux-foundation.org \
    --cc=david@fromorbit.com \
    --cc=fengguang.wu@intel.com \
    --cc=hch@infradead.org \
    --cc=jens.axboe@oracle.com \
    --cc=jlayton@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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