From: Andreas Dilger <adilger@clusterfs.com>
To: folkert@vanheusden.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: tool for testing how fast your kernel can rename files :-)
Date: Mon, 20 Jan 2003 10:54:47 -0700 [thread overview]
Message-ID: <20030120105447.N1594@schatzie.adilger.int> (raw)
In-Reply-To: <Pine.LNX.4.33.0301201826120.13207-100000@muur.intranet.vanheusden.com>; from folkert@vanheusden.com on Mon, Jan 20, 2003 at 06:29:25PM +0100
On Jan 20, 2003 18:29 +0100, folkert@vanheusden.com wrote:
> This night, while half a-sleep I thought it is usefull to have a tool
> which creates a number of files in a directory and then starts to randomly
> rename them. During this, it should output how much it has done and how
> many renames per second it did.
> 5 minutes back I programmed such a program, you can download it from:
> http://www.vanheusden.com/Linux/rename_test-1.0.tgz
>
> But now, fully awake with at least 8 cups of coffee in my system I cannot
> think of anything usefull this program is actually doing.
> Well, maybe to test if something gets corrupted allong the way?
For sure correctness is important (we use all sorts of benchmarks like
this to try and exercise our filesystem code), but also performance
measurement is important too. For example, mailservers do lots of file
renames to push mail through various stages in the delivery pipeline.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2003-01-20 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-20 17:29 folkert
2003-01-20 17:54 ` Andreas Dilger [this message]
2003-01-20 20:36 ` Cliff White
2003-01-20 21:11 ` Folkert van Heusden
2003-01-21 1:43 ` Rik van Riel
2003-01-21 9:13 ` Nikita Danilov
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=20030120105447.N1594@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=folkert@vanheusden.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
all inboxes | Powered by JetHome®