From: Matthias Schniedermeyer <ms@citd.de>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: Shawn Bohrer <shawn.bohrer@gmail.com>, xfs@oss.sgi.com
Subject: Re: High latencies writing to a memory mapped file
Date: Tue, 27 Jul 2010 13:27:00 +0200 [thread overview]
Message-ID: <20100727112700.GA26093@citd.de> (raw)
In-Reply-To: <20100727124750.30bb3209@harpe.intellique.com>
On 27.07.2010 12:47, Emmanuel Florac wrote:
> Le Tue, 27 Jul 2010 11:24:52 +0200
> Matthias Schniedermeyer <ms@citd.de> écrivait:
>
> > In case anybody has an idea what i could do to identify and/or
> > isolate the root-cause, i'm open for suggestions.
> >
>
> I'd thought that the io scheduler is the culprit. I've generally found
> that the default CFQ scheduler (default) is terrible for file servers.
I have 'deadline'ed the server, if that is the culprit then i will
"know" in about a month. (As i don't know how to force the problem i can
only wait for the problem not to happen. :-| )
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-07-27 11:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 14:47 High latencies writing to a memory mapped file Shawn Bohrer
2010-07-22 23:28 ` Dave Chinner
2010-07-26 22:09 ` Shawn Bohrer
2010-07-26 23:22 ` Dave Chinner
2010-08-03 22:03 ` Shawn Bohrer
2010-07-27 9:24 ` Matthias Schniedermeyer
2010-07-27 10:47 ` Emmanuel Florac
2010-07-27 11:27 ` Matthias Schniedermeyer [this message]
2010-07-27 13:06 ` Emmanuel Florac
2010-07-27 13:00 ` Stan Hoeppner
[not found] ` <4C4EDEFD.7000401@hardwarefreak.com>
2010-07-27 14:49 ` Matthias Schniedermeyer
2010-07-27 19:59 ` Kinzel, David
2010-07-27 21:02 ` Matthias Schniedermeyer
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=20100727112700.GA26093@citd.de \
--to=ms@citd.de \
--cc=eflorac@intellique.com \
--cc=shawn.bohrer@gmail.com \
--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