From: "Dan Maas" <dmaas@dcine.com>
To: "Ben Israel" <ben@genesis-one.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Disk Performance
Date: Sat, 10 Nov 2001 03:03:37 -0500 [thread overview]
Message-ID: <01bf01c169be$34305510$1a01a8c0@allyourbase> (raw)
In-Reply-To: <fa.jmrptbv.1dh8ur1@ifi.uio.no>
> Why does my 40 Megabyte per second IDE drive, transfer
> files at best at 1-2 Megabytes per second?
Keep in mind that some disk benchmarks just read/write long contiguous
regions of the disk, whereas the files you are copying may be fragmented.
So, while your drive may be able to sustain 40 MB/sec on a contiguous
region, it might slow down a lot if it has to seek to different parts of a
fragmented file, or between many files.
Actually while I'm on this subject - does anyone have experience with
"preallocating" files for low-latency transfers? e.g. if I know I'm going to
capture several GB of video to disk, will it reduce I/O latency if I
truncate the destination file to the proper size and fill it with zeros
beforehand? (I assume it helps for the fs to be as empty as possible) Are
any filesystems particularly good/bad for cases like this?
Regards,
Dan
next parent reply other threads:[~2001-11-10 8:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.jmrptbv.1dh8ur1@ifi.uio.no>
2001-11-10 8:03 ` Dan Maas [this message]
2001-11-10 1:21 Disk Performance Torrey Hoffman
2001-11-10 16:47 ` Davidovac Zoran
2001-11-10 17:51 ` Erik Andersen
-- strict thread matches above, loose matches on Subject: below --
2001-11-09 21:04 Ben Israel
2001-11-09 22:31 ` Rik van Riel
2001-11-09 22:53 ` Erik Andersen
2001-11-09 22:57 ` Rik van Riel
2001-11-09 23:20 ` Erik Andersen
2001-11-09 23:45 ` Matthias Schniedermeyer
2001-11-11 19:24 ` Maxwell Spangler
2001-11-11 21:52 ` Andre Hedrick
2001-11-11 20:56 ` Maxwell Spangler
2001-11-11 22:17 ` Andre Hedrick
2001-11-12 6:02 ` Erik Andersen
2001-11-09 23:24 ` Alan Cox
2001-11-09 22:35 ` Doug McNaught
2001-11-09 23:33 ` Stefan Smietanowski
2001-11-09 23:50 ` Ben Greear
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='01bf01c169be$34305510$1a01a8c0@allyourbase' \
--to=dmaas@dcine.com \
--cc=ben@genesis-one.com \
--cc=linux-kernel@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