All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Dan Oglesby <d.oglesby@insightbb.com>
Cc: reiserfs-list@namesys.com, demidov <demidov@thebsh.namesys.com>
Subject: Re: ReiserFS v3 + millions of files?
Date: Mon, 27 Oct 2003 12:38:38 +0300	[thread overview]
Message-ID: <3F9CE79E.60205@namesys.com> (raw)
In-Reply-To: <200310262146.28850.d.oglesby@insightbb.com>

I have unsubstantiated suspicions about VFS/dcache scalability.  It 
would be interesting to try to determine such things as how much of ram 
is consumed by dcache, etc.

Mr. Demidov, how long until sys_reiser4() can be used to create a 
million files sized 60k using lnodes?  It would be an interesting 
benchmarking experiment.....

sys_reiser4() sidesteps dcache....

Hans

Dan Oglesby wrote:

>Greetings...
>
>Long time ReiserFS user, first time I've had a problem.  Signed up for the 
>mailing list last week, and was surprised to see so little traffic (might be 
>a good thing?).
>
>I'm running Red Hat 7.3 using a Red Hat 2.4.20 kernel.  The system has a 
>RAID-5 array via 3Ware 7500 controller, and three Western Digital 120GB 
>"Special Edition" hard drives.  The array is one filesystem, ReiserFS.  The 
>operating system, swap, and other files are stored on a hard drive that is on 
>the primary IDE controller off of the motherboard.
>
>The system is a single board computer, with a P4 3.06 GHz hyperthreaded 
>processor (kernel is SMP enabled), 512MB of RAM, and contains a mix of 
>ReiserFS and EXT2 filesystems on the primary drive (ReiserFS only on the 
>array).  No NFS.
>
>The array is used to store what will basically amount to more than one million 
>files with an average size of sixty kilobytes.
>
>During simulations for file writes, I'm seeing write performance begin to drop 
>dramatically after 800,000 files have been stored on the filesystem.
>
>The filesystem is being mounted with the following options:  
>defaults,notail,noatime,nodiratime
>
>The filesystem was created with default options, basically a "mkreiserfs /dev/
>sda1".
>
>Is this behavior I should expect from ReiserFS v3?
>
>This week I will be switching from a Red Hat kernel to a vanilla kernel (from 
>kernel.org), first the latest 2.4 kernel, then the latest 2.6 kernel.  After 
>that...  I dunno.
>
>Help?
>
>--Dan Oglesby
>
>
>
>  
>


-- 
Hans



  parent reply	other threads:[~2003-10-27  9:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27  3:46 ReiserFS v3 + millions of files? Dan Oglesby
2003-10-27  6:55 ` Hans Reiser
2003-10-27  9:38 ` Hans Reiser [this message]
2003-10-27 11:42 ` Nikita Danilov
2003-10-27 16:03   ` Object Oriented FS darren
2003-10-27 18:23     ` Hans Reiser
2003-10-27 18:43       ` Mike Young
2003-10-27 19:01         ` Hans Reiser
2003-10-27 18:56       ` Andreas Dilger
2003-10-28  1:40         ` Steven Cole
2003-10-28  4:46     ` lrc1
2003-10-29  6:03 ` ReiserFS v3 + millions of files? Todd Lyons
2003-10-29  8:44   ` Hans Reiser
2003-10-30  6:04     ` Todd Lyons
2003-10-30  7:33       ` Andreas Dilger
  -- strict thread matches above, loose matches on Subject: below --
2003-10-28 14:50 Dan Oglesby

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=3F9CE79E.60205@namesys.com \
    --to=reiser@namesys.com \
    --cc=d.oglesby@insightbb.com \
    --cc=demidov@thebsh.namesys.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.