From: Andi Kleen <andi@firstfloor.org>
To: Michael Stiller <ms@2scale.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: howto boost write(2) performance?
Date: 09 Oct 2007 16:56:09 +0200 [thread overview]
Message-ID: <p73odf849rq.fsf@bingen.suse.de> (raw)
In-Reply-To: <1191937817.3641.9.camel@blackberry>
Michael Stiller <ms@2scale.net> writes:
>
> The write(2) performance is not good enough, the writer threads take to
> much time, and i ask you for ideas, howto to boost the write
> performance.
You could use an O_DIRECT write if the data is suitably aligned
and your IO sizes are big enough (O_DIRECT is usually a loss
on small IOs). It will also be synchronous, but if you do it
from a separate thread anyways that should be fine.
-Andi
next prev parent reply other threads:[~2007-10-09 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 13:50 howto boost write(2) performance? Michael Stiller
2007-10-09 10:25 ` Nick Piggin
2007-10-10 6:26 ` Michael Stiller
2007-10-09 14:19 ` Gustavo Chain
2007-10-09 14:56 ` Andi Kleen [this message]
2007-10-09 15:42 ` Boaz Harrosh
2007-10-09 16:26 ` Michael Tokarev
2007-10-11 13:50 ` Michael Stiller
2007-10-17 22:19 ` Bill Davidsen
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=p73odf849rq.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ms@2scale.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.