From: Willy Tarreau <willy@w.ods.org>
To: Timothy Miller <miller@techsource.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: File system performance, hardware performance, ext3, 3ware RAID1, etc.
Date: Fri, 13 Feb 2004 06:53:50 +0100 [thread overview]
Message-ID: <20040213055350.GG29363@alpha.home.local> (raw)
In-Reply-To: <402C0D0F.6090203@techsource.com>
On Thu, Feb 12, 2004 at 06:32:31PM -0500, Timothy Miller wrote:
> For writes, iozone found an upper bound of about 10megs/sec, which is
> abysmal. Typically, I'd expect writes to be faster (on a single drive)
> than reads, because once the write is sent, you can forget about it.
> You don't have to wait around for something to come back, and that
> latency for reads can hurt performance. The OS can also buffer writes
> and reorder them in order to improve efficiency.
It depends on the disk too. Lots of disks (specially IDE) are far slower
on writes than they are on reads.
> The 3ware has this write cache that you can turn on or off. With it
> off, it ensures that writes make it to the disks in order. With it on,
> it will reorder writes more efficiently. However, I noticed that the
> performance only went up to about 16meg/sec with the cache ON.
I don't think that the FS type has much importance once the cache is ON.
> IMPORTANT QUESTION: Is there any metadata anywhere in the swap
> partition (when it's not in use) that I need to save before I fill it
> with zeros?
No, there's nothing to save, but you'll have to rebuild the swap at the
end of your tests : mkswap /dev/sga3
I too often use the swap partition for testing purpose or for temporary
storage ; it's easy to do a swapoff; mke2fs on it :-)
> Also, what do I use as a source for zeros when writing with dd?
> "/dev/zero"?
yes. but don't try to copy any file from the disk onto this partition,
because head seeks will slow things down.
> What's the command? How about this:
> time dd if=/dev/zero of=/dev/sga3 bs=1024 count=1024
do it like this, but use higher values, particularly for bs which is only
1kB here. Using something like bs=65536 and count=4096 will give you a 256 MB
file.
> Will that do it? Should I use an offset to avoid any kind of header or
> metadata?
not needed. Just ensure that you write to the right partition, and better
check twice.
Regards
Willy
next prev parent reply other threads:[~2004-02-13 5:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 23:32 Timothy Miller
2004-02-13 5:53 ` Willy Tarreau [this message]
2004-02-13 19:19 ` Timothy Miller
2004-02-13 22:39 ` Willy Tarreau
2004-02-13 23:14 ` Timothy Miller
2004-02-13 19:30 ` Eric D. Mudama
2004-02-13 19:55 ` Linus Torvalds
2004-02-13 20:44 ` John Bradford
2004-02-13 22:45 ` Willy Tarreau
2004-02-13 12:23 Daniel Blueman
2004-02-13 14:27 ` Jamie Lokier
2004-02-13 14:44 ` Daniel Blueman
2004-02-13 16:15 ` Bartlomiej Zolnierkiewicz
2004-02-13 22:56 ` Timothy Miller
2004-02-14 18:16 Walt H
2004-02-16 17:53 ` Timothy Miller
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=20040213055350.GG29363@alpha.home.local \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.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®