I actually think that as long as you start splitting files across directories to keep from getting more than 1000 in a single dir, both file system and Berkeley would scale very far without a huge difference in performance. Remember, BerkeleyDB handles databases with terabytes of data.

There are definitely many advabtages to having things in normal files, especially for text content, and it's the only choice for NFS or other file servers.

I did use the DB_INIT_CDB flag, which initialized the concurrency methods. If I leave that off, BerkeleyDB gets faster, but you lose the ability to do concurrent access. I didn't think the test would be very interesting if it used options that didn't allow for concurrency.

In reply to Re: Re: BerkeleyDB vs. Linux file system by perrin
in thread BerkeleyDB vs. Linux file system by perrin

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.