Add new comment

Submitted by Patrick (not verified) on Tue, 2008-02-05 14:52.

"He has seen the Loom database file get 20 times bigger than it needed to be."

Only under extreme repeated cycles of deletion and insertion. Also, this did not happen in the Loom database itself, but in a database on another server where we run a hedge fund accounting business. There we have a particular application which deletes a massive recursive structure and re-creates it from scratch. Repeated runs of that application would cause "holes" in the database file which apparently were difficult to re-use in a timely manner -- hence the expansion of the database file.

The GDBM database is one of the fastest, simplest, and most reliable pieces of code I've seen. The only drawback I have seen is the fragmentation under extreme circumstances, and that drawback is neatly avoided with the incremental copy technique.

Reply



The content of this field is kept private and will not be shown publicly.


*

  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <i> <b> <u>
  • Lines and paragraphs break automatically.
  • Web and e-mail addresses are automatically converted into links.
  • You may quote other posts using [quote] tags.
  • Easily link to terms in various wikis. For help, see interwiki.
  • Easily link to terms in various wikis. For help, see interwiki.
  • You may quote other posts using [quote] tags.
  • You can use BBCode tags in the text, URLs will be automatically converted to links
Verify comment authorship
Captcha Image: you will need to recognize the text in it.
*
Please type in the letters/numbers that are shown in the image above.