I have a couple of patches to to 1.25, which will work around this
problem.
The real problem is that the current implementation writes the entire
datastore to
disk, after each put, delete, or transaction. One tradeoff you can
make is, "not" to
guarrantee the transactions, by persisting to disk
On Sun, Oct 11, 2009 at 2:06 PM, (jpgerek) wrote:
> Does anyone have a solution or workaround apart from working with a
> reduced data set ?
There's nothing to do with the current implementation which is indeed
very simple and can't handle large data sets (everything is loaded
into memory and the
