[EMAIL PROTECTED] wrote:
Hi there,
we are on an challanging project with very high requirements on performance.
When doing some debugging we discover, that the sqlite method for creating
an memory-based database is much slower than using e.g /dev/shm on linux or
/tempfs on solaris. (We have measured an 20min performance advantage for the
/dev/shm style on a batch run which takes 70min with :memory: and just 49min
using /dev/shm.
Because our project needs to be ported to windows - the /dev/shm is not an
option - because win2000 does not support any temporary memory based file
system. But beside that, we guess, that there will be a possiblity to tune
:memory: or we belief, that we to something wrong when using :memory: (for
example pragma page_size ...).
Is there any body who can give us some advises to tune up our :memory:
database to become as fast as the /dev/shm alternativ?
Roland,
There was a previous thread about the speed of :memory: databases that
you may want to look for. Basically, SQLite3 is actually slightly
slower using a :memory: database than an actual file on both Windows and
Linux. This changed when the SQLite stared using the same pager for both
memory and file based databases. If you want better memory performance,
and don't need any of the newest features, you might want to look at
using SQLite version 2 instead. It was significantly faster when using a
memory based store since it had a separate, purpose designed, memory pager.
HTH
Dennis Cote
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
