From: Dave Chinner <david@fromorbit.com>
To: Markus Stockhausen <stockhausen@collogia.de>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Writeback Stalls
Date: Thu, 20 Sep 2012 16:05:43 +1000 [thread overview]
Message-ID: <20120920060543.GH31501@dastard> (raw)
In-Reply-To: <12EF8D94C6F8734FB2FF37B9FBEDD1735831B7C9@EXCHANGE.collogia.de>
On Thu, Sep 20, 2012 at 04:33:09AM +0000, Markus Stockhausen wrote:
> > Fundamentally, you are doing it all wrong. High throughput, low
> > latency NFS servers write dirty data to disk fast, not leave it
> > memory until you run out of clean memory because that causes
> > everything to block waiting for writeback IO completion to be ale to
> > free memory...
>
> Maybe I did not make it clear enough.
Plenty clear enough. Maybe I did not make it clear enough:
Nobody has the time to try to diagnose a problem on a configuration
that is obviously broken and pessimal for writeback behaviour. The
first step is to report your actual problem, not an artificial
behaviour you *think* demonstrates the same problem....
> The above setup is only
> for demonstration purposes. To expose the problem better. In
> real life we can see stalls tat thange from 0.5-1 seconds. Even
> with all caches active, small dirty writeback settings and unlimited
> bandwidth.
So describe the application, etc that you see this problem. Start
with:
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
and we can go from there.
> In between I found others complaining about the same problem:
>
> http://lwn.net/Articles/486313/
> http://oss.sgi.com/archives/xfs/2011-09/msg00189.html
How do you know they are the same problem?
Indeed, they aren't even writeback problems - they are application
IO latency issues caused by the introduction of stable pages during
writeback.
> So just one last question: Can I savely revert the the mentioned
> commit d76ee18a8551e33ad7dbd55cac38bc7b094f3abb if I only
> write data to a battery backed up hardware raid controller on a
> server that is attached to an UPS?
NFS servers don't use mmap, so that patch is not causing your
writeback problems.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-09-20 6:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 18:36 Writeback Stalls Markus Stockhausen
2012-09-19 21:34 ` Dave Chinner
2012-09-20 4:33 ` Markus Stockhausen
2012-09-20 6:05 ` Dave Chinner [this message]
2012-09-20 7:12 ` Emmanuel Florac
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=20120920060543.GH31501@dastard \
--to=david@fromorbit.com \
--cc=stockhausen@collogia.de \
--cc=xfs@oss.sgi.com \
/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