Just trying to lay some breadcrumbs for others, since I don't see any definitive statements about this in the archives...
Is there any mechanism for compacting jdbm files? Briefly looking at the implementation leads me to think that deleting records (and, presumably by extension, removing mappings from HTree, etc) just adds blocks to a free list, where they would be picked up by future puts, etc. However, that doesn't *seem* to be the case: I've got a process that pushes a ton of data into a jdbm file; deleting all of it later on and then repeating the load with identical data doubles the file's size. Is there a configuration option I'm missing, am I likely doing something wrong in general, or have I misunderstood the nature of jdbm's storage re-use policy? If the latter, is there a vacuum process (or similar) floating around so I can shrink a file when desired? Thanks, - Chas ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Jdbm-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jdbm-general
