From: Roger Heflin <rogerheflin@gmail.com>
To: Lukas Hejtmanek <xhejtman@ics.muni.cz>
Cc: Jan Engelhardt <jengelh@computergmbh.de>, linux-kernel@vger.kernel.org
Subject: Re: Disk schedulers
Date: Fri, 15 Feb 2008 11:36:25 -0600 [thread overview]
Message-ID: <47B5CD99.5010301@gmail.com> (raw)
In-Reply-To: <20080215155922.GD4269@ics.muni.cz>
Lukas Hejtmanek wrote:
> On Fri, Feb 15, 2008 at 03:42:58PM +0100, Jan Engelhardt wrote:
>> Also consider
>> - DMA (e.g. only UDMA2 selected)
>> - aging disk
>
> it's not the case.
>
> hdparm reports udma5 is used, if it is reliable with libata.
>
> The disk is 3 months old, kernel does not report any errors. And it has never
> been different.
>
A new current ide/sata disk should do around 60mb/second, check the
min/max bps rate listed on the disk companies site, and divide by 8, and
take maybe 80% of that
Also you may consider using the -l option on the scp command to limit
its total usage.
This feature has been around at least 8 years (from 2.2) that high
levels of writes would significantly starve out reads, mainly because
you can queue up 1000's of writes, and a read, when the read
finishes there are another 1000's writes for the next read to
get in line behind, and wait, and this continues until the
writes stop.
Roger
next prev parent reply other threads:[~2008-02-15 17:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 16:21 Disk schedulers Lukas Hejtmanek
2008-02-15 0:02 ` Tejun Heo
2008-02-15 10:09 ` Lukas Hejtmanek
2008-02-15 14:42 ` Jan Engelhardt
2008-02-15 14:57 ` Prakash Punnoor
2008-02-15 17:11 ` Zan Lynx
2008-02-15 21:32 ` FD Cami
2008-02-16 16:13 ` Lukas Hejtmanek
2008-02-20 17:04 ` Zdenek Kabelac
2008-02-15 15:59 ` Lukas Hejtmanek
2008-02-15 16:22 ` Jeffrey E. Hundstad
2008-02-15 17:36 ` Roger Heflin [this message]
2008-02-15 17:24 ` Paulo Marques
2008-02-16 16:15 ` Lukas Hejtmanek
2008-02-16 17:20 ` Pavel Machek
2008-02-20 18:48 ` Lukas Hejtmanek
2008-02-21 23:50 ` Giuliano Pochini
2008-02-17 19:38 ` Linda Walsh
2008-02-28 17:14 ` 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=47B5CD99.5010301@gmail.com \
--to=rogerheflin@gmail.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=xhejtman@ics.muni.cz \
/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