From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: Dmitri Monakhov <dmonakhov@openvz.org>
Cc: linux-fsdevel@vger.kernel.org, jens.axboe@oracle.com
Subject: Re: write is faster whan seek?
Date: Wed, 11 Jun 2008 07:38:21 -0400 [thread overview]
Message-ID: <484FB92D.4090808@hp.com> (raw)
In-Reply-To: <m3r6b4zbdf.fsf@dmon-lap.sw.ru>
Dmitri Monakhov wrote:
Could it be that in the first case you will have merges, thus creating
fewer/larger I/O requests? Running iostat -x during the two runs, and
watching the output is a good first place to start.
Alan
next prev parent reply other threads:[~2008-06-11 11:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 7:20 write is faster whan seek? Dmitri Monakhov
2008-06-11 7:48 ` Jens Axboe
2008-06-11 8:11 ` Dmitri Monakhov
2008-06-11 8:26 ` Jens Axboe
2008-06-11 9:28 ` Dmitri Monakhov
2008-06-11 9:38 ` Jens Axboe
2008-06-11 11:38 ` Alan D. Brunelle [this message]
2008-06-11 11:49 ` Jens Axboe
2008-06-11 11:52 ` Alan D. Brunelle
2008-06-11 11:55 ` Jens Axboe
2008-06-16 12:14 ` Dmitri Monakhov
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=484FB92D.4090808@hp.com \
--to=alan.brunelle@hp.com \
--cc=dmonakhov@openvz.org \
--cc=jens.axboe@oracle.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).