From: Anthony Truong <Anthony.Truong@mascorp.com>
To: John Newbie <john_r_newbie@hotmail.com>
Cc: vda@port.imtp.ilyichevsk.odessa.ua, linux-kernel@vger.kernel.org
Subject: Re: ide drives performance issues, maybe related with buffer cach e.
Date: Thu, 14 Aug 2003 18:52:16 -0700 [thread overview]
Message-ID: <1060912337.31243.49.camel@huykhoi> (raw)
On Fri, 2003-08-15 at 23:39, John Newbie wrote:
> > So question is : why when i am copying file from one HD to another
(for
> > simplicity from /hda to /hdb)
> > the speed fall down ? Starting from about 27-30 MB/s (drives are in
>UDMA-4,
> > hdparm -X68) it drops
> > down to 11-12 MB/s after 4-5s. In *indows transfer rate is almost
>constant
> > and about 20-22 MB/s (same hardware). Why the h#ll we suck?
> > I feel that it's due to buffer cache, because when you use sync
(while
> > copying) transfer rate is so small or even 0.
> > Drives are tuned with hdparm to highest transfer rates, readahead,
>multiple
> > sector count (hdparm
> > for details).
> > Tried different filesystems, from classic ext2/3 to modern
xfs/reiserfs.
>The
> > same results.
> > Pure kernel from kernel.org (2.4.{19,20,21}), vendors kernels - all
the
>How do you copy files? cp? dd? Midnight Commander? ;)
>Does it happen with SCSI?
>--
>vda
I've used cp & Midnight Commander (mc). Also when someone uploads big
file
on server through
samba, speed sometimes fall down to zero.
Have no idea about scsi, drives are IDE.
Hello,
Let's see if we can eliminate this HW constraint:
Do you have the 2 HDs at the same IDE port (primary or secondary) or at
different IDE ports?
It might be related to the fact that IDE driver can't send 2
simultaneous cmds to 2 different drives if they are attached to the same
IDE port.
This is a simple point, but I hope we don't overlook it when making the
comparison between Linux and *dows. :-)
Regards,
Anthony Dominic Truong.
Disclaimer: The information contained in this transmission, including any
attachments, may contain confidential information of Matsushita Avionics
Systems Corporation. This transmission is intended only for the use of the
addressee(s) listed above. Unauthorized review, dissemination or other use
of the information contained in this transmission is strictly prohibited.
If you have received this transmission in error or have reason to believe
you are not authorized to receive it, please notify the sender by return
email and promptly delete the transmission.
reply other threads:[~2003-08-15 16:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1060912337.31243.49.camel@huykhoi \
--to=anthony.truong@mascorp.com \
--cc=john_r_newbie@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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®