Gnus development mailing list
 help / color / mirror / Atom feed
From: bmiller@cs.umn.edu (Brad Miller)
Cc: ding@ifi.uio.no
Subject: Re: nndb mailing list?
Date: 03 Apr 1996 21:18:59 -0600	[thread overview]
Message-ID: <y0aybocfzh8.fsf@caesar.cs.umn.edu> (raw)
In-Reply-To: Dave Blacka's message of 29 Mar 1996 12:13:38 -0700

>>>>> "Dave" == Dave Blacka <dblacka@fuentez.com> writes:

>>>>> "Joe" == Joe Hildebrand <hildjj@fuentez.com> writes:
Joe> Also BTW, we did some more testing on the differences between gdbm and
Joe> berkeley db.  Gdbm wins *big* on disk space (like one less digit in
Joe> the bytes column), and is not noticeably slower.  It will probably be
Joe> the default in 0.8.  We'll also include a script to convert one to the
Joe> other.

Dave> Ok.  Joe lied here a bit.  GDBM does actually win big on disk space:
Dave> Berkeley DB isn't really very space efficient when the data you are
Dave> storing has widely different sizes (like mail bodies), so the Berkely
Dave> DB file grows to enormous size.  For instance, I probably have at most
Dave> 1 Meg of mail stored in a 7 MB mail.db file.  GDBM gets you much
Dave> closer to the actual size of the data.  However, GDBM and Berkeley DB
Dave> only have comparable speeds when you are hitting a local disk.  In my
Dave> testing so far, GDBM suffers from incredible performance problems over
Dave> NFS, while Berkeley DB behaves about the same.  Thus, if you are
Dave> storing your mail.db file on a local disk, switching over to GDBM is
Dave> probably a real good idea, otherwise it would probably be best to wait
Dave> until Joe and I rework the whole backend of nndb.

The GroupLens Better Bit Bureau uses gdbm as its database, and I can
vouch for the fact that performance over NFS is really really bad.
Also, if you happen to get into a situation where you are frequently
updating the data associated with one key, the database will start to
grow all out of proportion.  The only solution to this seems to be to
call gdbm_reorganize, but that is terribly slow.  I've had some database
files go from 46Meg back down to 8Meg with one call to reorg!

\Brad
----------------------------------------------------------------------------
Brad Miller                    | e-mail: bmiller@cs.umn.edu
University of Minnesota        | phone:  (612) 626-8396     
Department of Computer Science | www:    http://www.cs.umn.edu/~bmiller
EE/CS 5-244                    | 
----------------------------------------------------------------------------
**  Save USENET Try GroupLens: http://www.cs.umn.edu/Research/GroupLens   **
----------------------------------------------------------------------------


  reply	other threads:[~1996-04-04  3:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-03-28 16:38 Joe Hildebrand
1996-03-28 19:53 ` Greg Thompson
1996-03-28 21:09   ` Dave Blacka
1996-03-28 21:41   ` David Kågedal
1996-03-28 22:14     ` Joe Hildebrand
1996-03-28 22:56       ` Thomas Neumann
1996-03-28 21:07 ` Colin Rafferty
1996-03-29  5:42 ` Lars Magne Ingebrigtsen
1996-03-29  7:04   ` Jason L Tibbitts III
1996-03-29 15:58     ` Joe Hildebrand
1996-03-29 19:13       ` Dave Blacka
1996-04-04  3:18         ` Brad Miller [this message]
1996-04-04 18:32           ` David Blacka

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=y0aybocfzh8.fsf@caesar.cs.umn.edu \
    --to=bmiller@cs.umn.edu \
    --cc=ding@ifi.uio.no \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).