*** 1,6 **** --- 1,9 ---- This page is about using in-memory SQLite databases. ---- + 2007-04-16: Is there a way to forcibly suspend file writes on a temporary basis? Basically, if there is some process that cannot be slowed down by disk writes (media playback), but we will be issuing INSERT and UPDATEs to the database, is there a way to have those transactions not be commited to file, but keep those changes in-memory? It seems that we could keep the 'dirtyCache' flag set to zero when we're in this mode and it would not perform writes (that's in testing now). We don't want to have to maintain two databases (one in-memory and one on-disk, shuffling rows between the two) and simply suspending disk writes would solve a lot of problems here. + + ---- 2007-04-16: I have run a simple test to compare the performance of disk-based database and memory-resident database in sqlite3, the result was the same as the wiki item at 2006-09-08 said. Why the memory-resident database is so slow? Is there any way to improve it? ----
Small. Fast. Reliable.
Choose any three.
Choose any three.
|
|