On 22 Feb 2013, at 8:07, Stephen Chrzanowski wrote:
I think I missed something;
For clarification, you mention that you're running the tests and are
monitoring memory use but (And here's what I'm missing) you don't see
a
memory load against the application?
I do see a memory load against the application. It goes from about 1MB
to about 10MB as the database gets populated. It's definitely doing what
I expect in terms of storing things in memory, it's not swapping.
With SQLite 3.6, this makes it dramatically slower. With 3.7, speed is
roughly the same.
You mention indexes. Are these just basic Unique constraints, or,
standard
indexes? How many records are in the database, say on medium to heavy
load?
A couple of actual indexes. Most of my tests ended up with 28,000
records, but I did some with 84,000 or so (3x the size), whereupon
memory usage went up to 20-something MB. Disk performance was unchanged,
memory performance was about a factor of 2-3 worse.
-s
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
