From: "Bhanu Kalyan Chetlapalli" <chbhanukalyan@gmail.com>
To: "Manish Regmi" <regmi.manish@gmail.com>
Cc: "Nick Piggin" <nickpiggin@yahoo.com.au>,
kernelnewbies@nl.linux.org, linux-kernel@vger.kernel.org
Subject: Re: Linux disk performance.
Date: Fri, 22 Dec 2006 05:44:54 +0530 [thread overview]
Message-ID: <7d15175e0612211614y3ce090fcn38cbcaced76b1024@mail.gmail.com> (raw)
In-Reply-To: <652016d30612200317i6d33d097xe55971750e83cd97@mail.gmail.com>
On 12/20/06, Manish Regmi <regmi.manish@gmail.com> wrote:
> On 12/19/06, Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> > When you submit a request to an empty block device queue, it can
> > get "plugged" for a number of timer ticks before any IO is actually
> > started. This is done for efficiency reasons and is independent of
> > the IO scheduler used.
> >
>
> Thanks for the information..
>
> > Use the noop IO scheduler, as well as the attached patch, and let's
> > see what your numbers look like.
> >
>
> Unfortunately i got the same results even after applying your patch. I
> also tried putting
> q->unplug_delay = 1;
> But it did not work. The result was similar.
I am assuming that your program is not seeking inbetween writes.
Try disabling the Disk Cache, now-a-days some disks can have as much
as 8MB write cache. so the disk might be buffering as much as it can,
and trying to write only when it can no longer buffer. Since you have
an app which continously write copious amounts of data, in order,
disabling write cache might make some sense.
> --
> ---------------------------------------------------------------
> regards
> Manish Regmi
>
Bhanu
> ---------------------------------------------------------------
> UNIX without a C Compiler is like eating Spaghetti with your mouth
> sewn shut. It just doesn't make sense.
>
> --
> Kernelnewbies: Help each other learn about the Linux kernel.
> Archive: http://mail.nl.linux.org/kernelnewbies/
> FAQ: http://kernelnewbies.org/faq/
>
>
--
There is only one success - to be able to spend your life in your own way.
next prev parent reply other threads:[~2006-12-22 0:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 4:07 Manish Regmi
2006-12-18 8:35 ` Arjan van de Ven
2006-12-18 12:39 ` Manish Regmi
2006-12-18 12:54 ` Nick Piggin
2006-12-18 13:07 ` Erik Mouw
2006-12-19 6:22 ` Manish Regmi
2006-12-19 6:38 ` Nick Piggin
2006-12-19 12:18 ` Arjan van de Ven
2006-12-20 11:17 ` Manish Regmi
2006-12-22 0:14 ` Bhanu Kalyan Chetlapalli [this message]
2006-12-22 5:30 ` Manish Regmi
2006-12-22 5:39 ` Bhanu Kalyan Chetlapalli
2006-12-22 5:56 ` Manish Regmi
2006-12-20 22:29 ` Bill Davidsen
2006-12-21 6:03 ` Manish Regmi
2006-12-21 7:15 ` Daniel Cheng
2006-12-21 13:22 ` Erik Mouw
2006-12-22 5:39 ` Manish Regmi
2006-12-27 15:50 ` Phillip Susi
2007-01-01 1:59 ` 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=7d15175e0612211614y3ce090fcn38cbcaced76b1024@mail.gmail.com \
--to=chbhanukalyan@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=regmi.manish@gmail.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
all inboxes | Powered by JetHome®