they used CREATE TABLE test (key blob, value blob, PRIMARY KEY(key)) CREATE INDEX keyindex ON test (key)
on random replaces it doubles the write operations. J Decker schrieb: > On Wed, Jul 27, 2011 at 6:22 PM, Stephan Wehner <stephanweh...@gmail.com> > wrote: >> There are some benchmark's at >> http://leveldb.googlecode.com/svn/trunk/doc/benchmark.html >> >> I don't have anything to point to, but I thought sqlite3 does better >> than stated there. >> >> In particular, 26,900 sequential writes per second and 420 random writes >> per second from section "1. Baseline Performance" look suspicious. >> > > Wow, that's a bad mark for sqlite; I dunno it's somewhat misleading, > because I do know that if I use sqlite as a logging database, and > stream data to it it's kinda slow, and works better if I bunch up > inserts with multiple value sets. But, enabling transactions, and > doing the same thing, write speed goes way up. And now with WAL > journal, it might affect that speed test also in auto transact mode > especially > >> What you say? >> >> Stephan >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@sqlite.org >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >> > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
