From: studdugie <studdugie@gmail.com>
To: Hans Reiser <reiser@namesys.com>
Cc: reiserfs-mailing-list <reiserfs-list@namesys.com>
Subject: Re: 15M files
Date: Fri, 19 Aug 2005 18:39:44 -0400 [thread overview]
Message-ID: <5a59ce53050819153961a71cde@mail.gmail.com> (raw)
In-Reply-To: <43065D7D.2000802@namesys.com>
I can't use V4 because I can't introduce an unstable kernel on the box
where the app is running.
On 8/19/05, Hans Reiser <reiser@namesys.com> wrote:
> studdugie wrote:
>
> >Hello. I'm looking to replace a couple Berkeley DB data stores w/
> >regular file system directories backed by reiserfs (3.6). The reason
> >is Berkeley DB is slow especially for data w/ little or no locality of
> >reference. I'm posting to this list because I would like to get some
> >opinions on if reiserfs is suitable for the job. Currently there are
> >15,079,597 records in 1 of the database. If I moved to a directory
> >based db it would result in 15,079,597 discreet files ranging in sizes
> >from 1 byte to 1kb. I was reading the FAQ on the namesys site and it
> >mentioned that the r5 hash supports 1,200,000 files w/o collision.
> >Since 15M is 12.5x greater I'm expecting massive amounts of
> >collisions. So the question becomes how bad should I expect it to be?
> >Should I assume the file system can handle it or slow to a crawl? I
> >would really appreciate some feedback from the experts before I go
> >ripping out the Berkeley DB code.
> >
> >Thanx.
> >
> >
> >
> >
> Use V4, it has much better hashiing.
>
next prev parent reply other threads:[~2005-08-19 22:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 21:49 15M files studdugie
2005-08-19 22:08 ` PFC
2005-08-19 22:09 ` David Masover
2005-08-19 22:44 ` studdugie
2005-08-20 9:58 ` Christian Iversen
2005-08-20 10:23 ` PFC
2005-08-20 12:51 ` Christian Iversen
2005-08-19 22:30 ` Hans Reiser
2005-08-19 22:39 ` studdugie [this message]
2005-08-19 22:45 ` David Masover
2005-08-19 22:50 ` Hans Reiser
2005-08-21 19:16 ` Lexington Luthor
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=5a59ce53050819153961a71cde@mail.gmail.com \
--to=studdugie@gmail.com \
--cc=reiser@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.