On 18 Jun 2009, at 2:15pm, Rizzuto, Raymond wrote: > I'm actually memory limited, which is why I am looking at moving > infrequently needed object to persistent store with sqlite3. I like > the idea of using the asynchronous i/o module so that the writing > can be done in a background thread, but still allow the main thread > to retrieve data that has been written or is in queue to be written.
Aren't those two things in conflict ? Caching and multiple concurrent threads are two features which chew up a great deal of memory: a cache /is/ memory, and each independent thread requires its own working-memory. If you're trying to minimise memory-usage you tend to have no caching and single threads. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
