From: Michael Marxmeier <mike@marxmeier.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: CMA <cma@mclink.it>, linux-kernel@vger.kernel.org
Subject: Re: e2fs performance as function of block size
Date: Wed, 22 Nov 2000 23:28:12 +0100 [thread overview]
Message-ID: <3A1C487C.30BDFE9F@marxmeier.com> (raw)
In-Reply-To: <E13yNlM-0005Q3-00@the-village.bc.nu>
Alan Cox wrote:
> I see higher performance with 4K block sizes. I should see higher
> latency too but have never been able to measure it. Maybe it depends
> on the file system.
> It certainly depends on the nature of requests
If the files get somewhat bigger (eg. > 1G) having a bigger block
size also greatly reduces the ext2 overhead. Especially fsync()
used to be really bad on big file but choosing a bigger block
size changed a lot.
If the database used by the original poster is based on
something like c-isam then (AFAIR) it is in fact using
1k blocks which may explain the better results of 1k block
size. With a 100 MB file size fs management overhead should
not be that visible.
Michael
--
Michael Marxmeier Marxmeier Software AG
E-Mail: mike@marxmeier.com Besenbruchstrasse 9
Phone : +49 202 2431440 42285 Wuppertal, Germany
Fax : +49 202 2431420 http://www.marxmeier.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-22 22:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 19:46 e2fs performance as function of block size CMA
2000-11-21 17:30 ` Reto Baettig
2000-11-21 23:34 ` Alan Cox
2000-11-22 0:06 ` Jeff V. Merkey
2000-11-22 0:27 ` Brian Pomerantz
2000-11-22 0:27 ` Alan Cox
2000-11-22 0:37 ` Jeff V. Merkey
2000-11-22 22:28 ` Michael Marxmeier [this message]
2000-11-24 13:11 ` Stephen C. Tweedie
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=3A1C487C.30BDFE9F@marxmeier.com \
--to=mike@marxmeier.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cma@mclink.it \
--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