From: Hans Reiser <reiser@namesys.com>
To: bill@billrees.com
Cc: reiserfs-list@namesys.com
Subject: Re: Degrading performance?
Date: Wed, 10 Apr 2002 22:10:08 +0400 [thread overview]
Message-ID: <3CB48000.1070805@namesys.com> (raw)
In-Reply-To: 20020410172502.29765.qmail@web10006.mail.yahoo.com
Bill Rees wrote:
>Hi,
>
>I've got a appication I'm testing that writes millions
>of 15K files to an 800gb raidset (5x160 gb Maxtor
>drives on a 3ware 7450 controller). The basic format
>of the directory structure is as follows:
>
>/partition/00/yyyymmdd/hhmm/file1 (15k)
>/partition/00/yyyymmdd/hhmm/file2 (15k)
>/partition/00/yyyymmdd/hhmm/file3 (15k)
>.
>.
>.
>/partition/00/yyyymmdd/hhmm/file1800 (15k)
>
>Where yyyymmdd is a date and hhmm is a time. My test
>program simulates a production system. I'm writing
>1800 files filled with nulls as fast as my CPU will
>allow for each subdirectory in an effort to fill the
>raidset.
>
>I compute the time in milliseconds that it takes to
>fill a directory with the 1800 files. As the disk
>fills, the number of megabytes the application can
>write per second gradually degrades from around 8.5
>mb/sec when the disk is 2% full to 1.3 mb/sec at 23%
>full. I tried the same test on a single 160gb disk
>and, although the performance was a bit better, the
>degradation is still there. A single 160gb formatted
>with ext2 does not seem to show this gradual
>degradation.
>
>Does this sound like normal behavior and does anyone
>have a suggestion on what could be done to optimize
>this? My production application can handle multiple
>partitions so I could break up the 800gb raid.
>
>Any help or suggestions would be appreciated.
>
>Bill
>
>
>
>
>
>=====
>Bill Rees - bill@billrees.com - http://billrees.com
>
>__________________________________________________
>Do You Yahoo!?
>Yahoo! Tax Center - online filing with TurboTax
>http://taxes.yahoo.com/
>
>
This is a very interesting measurement. Please experiment with the
patch to bitmap.c that Oleg is experimenting with (I think it was put on
the reiserfs mailing list recently).
I think you will find the various mount options of interest.
Hans
next prev parent reply other threads:[~2002-04-10 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 17:25 Degrading performance? Bill Rees
2002-04-10 18:10 ` Hans Reiser [this message]
2002-04-10 19:37 ` Oleg Drokin
2002-04-10 18:10 ` Hans Reiser
2002-04-10 19:37 ` Oleg Drokin
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=3CB48000.1070805@namesys.com \
--to=reiser@namesys.com \
--cc=bill@billrees.com \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.