I'd like to point out that files contain more info than simple key/value entries in BerkeleyDB.

I'd also like to point out that you cannot read/write N bytes at a time with BerkeleyDB.

Now here are results for

BerkeleyDB vs. NTFS

Benchmark: timing 10 iterations of berkeley write, file write...
berkeley write: 26 wallclock secs ( 0.92 usr +  1.16 sys =  2.08 CPU) 
+@  4.81/s (n=10)
file write: 54 wallclock secs ( 3.17 usr +  8.80 sys = 11.97 CPU) @  0
+.84/s (n=10)
               s/iter     file write berkeley write
file write       1.20             --           -83%
berkeley write  0.208           476%             --
Benchmark: timing 10 iterations of berkeley read, file read...
berkeley read:  2 wallclock secs ( 0.53 usr +  0.55 sys =  1.08 CPU) @
+  9.28/s (n=10)
 file read:  2 wallclock secs ( 1.88 usr +  0.89 sys =  2.77 CPU) @  3
+.62/s (n=10)
                Rate     file read berkeley read
file read     3.62/s            --          -61%
berkeley read 9.28/s          157%            --

E:\dev\LOOSE>perl BerkeleyDB.V.NTFS.pl
Benchmark: timing 10 iterations of berkeley write, file write...
berkeley write: 26 wallclock secs ( 0.94 usr +  1.20 sys =  2.14 CPU) 
+@  4.67/s (n=10)
file write: 52 wallclock secs ( 3.28 usr +  8.14 sys = 11.42 CPU) @  0
+.88/s (n=10)
               s/iter     file write berkeley write
file write       1.14             --           -81%
berkeley write  0.214           433%             --
Benchmark: timing 10 iterations of berkeley read, file read...
berkeley read:  1 wallclock secs ( 0.41 usr +  0.63 sys =  1.03 CPU) @
+  9.70/s (n=10)
 file read:  3 wallclock secs ( 1.84 usr +  0.89 sys =  2.73 CPU) @  3
+.66/s (n=10)
                Rate     file read berkeley read
file read     3.66/s            --          -62%
berkeley read 9.70/s          165%            --

$BerkeleyDB::VERSION = 4.0;
$BerkeleyDB::VERSION = 0.18;
# Microsoft Windows 2000 [Version 5.00.2195] (no other NTFS info avail
+able ;)

[download]

MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests.
** The Third rule of perl club is a statement of fact: pod is sexy.

In reply to Re: BerkeleyDB vs. Linux file system by PodMaster
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.