On Tuesday, April 29, 2014 03:38:57 AM Dan Kennedy wrote: > On 04/29/2014 03:53 AM, [email protected] wrote: > > I didn't know this list strips attachments, so the source file is here: > > > > http://derkarl.org/~charles/runlsm.cpp > > Thanks for this. It is a problem. > > LSM accumulates data in a tree structure in shared-memory until there is > "enough" (~1-2 MB) to flush through to the database file. But at the > moment, it can only flush data to the db file between transactions. And > the in-memory tree can only hold 2GB of data (including overhead). So > things fail if a single transaction exceeds that limit. In the short > term, it should be changed to return LSM_FULL for any transaction too > large to handle. But the real fix should be to change things so that LSM > can begin flushing data to the database file mid-transaction.
I'm also seeing a similar problem in which it silently discards entries, but I haven't been able to narrow down an example for you. Let me know if that would be helpful and I'll try harder. What could I do to improve LSM? Charles _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
