python+sqlite3 in memory database
denisg640 at gmail.com
Mon Aug 30 22:50:37 CEST 2010
Yep, I see what you are saying. I am going to do a bit more research to see
how sqlite3 works internally, ie. cache size, page size, etc, and then
decide if I will need to mess with in-memory databases.
Thanks for your insight, appreciate it.
On Mon, Aug 30, 2010 at 3:51 PM, Benjamin Peterson <benjamin at python.org>wrote:
> Denis Gomes <denisg640 <at> gmail.com> writes:
> > Hey Benjamin,
> > Take a look at this website I found about cached and in-memory
> databases. I
> think the gist of the article is that caching is good if you are doing
> on data that is frequently used whereas in-memory speeds up
> writes, (inserts and
> updates) to the db as well as querying. Maybe I am missing something?
> Well, of course, but there's little point to doing INSERTs and UPDATEs if
> don't write them to disk at some point. You could just have a long running
> transaction which will not write to the database file (though depending on
> you have sqlite setup it may write to a journal file) until you commit it.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-list