RE: [sqlite] Sharing an in-memory database between applications

Hi Rob, This maybe a dumb idea but have you tried a software RAM disk? Or maybe even a physical RAM disk. http://www.tomshardware.com/2005/09/07/can_gigabyte/index.html Kind Regards, Lodewijk -Original Message- From: Rob Richardson [mailto:[EMAIL PROTECTED] Sent: Friday, July 13, 20

RE: [sqlite] Sharing an in-memory database between applications

Hi Rob! Maybe standard windows feature memory-mapping-file can help you? Regards Xeepe Phone Solution Team http://en.xeepe.com -Original Message- From: Rob Richardson [mailto:[EMAIL PROTECTED] Sent: Friday, July 13, 2007 7:35 PM To: sqlite-users@sqlite.org Subject: [sqlite] Sharing a

Re: [sqlite] Sharing an in-memory database between applications

Hi Rob, On 7/13/07, Rob Richardson <[EMAIL PROTECTED]> wrote: Greetings! But I'm wondering if I can use an in-memory database to improve this dramatically. The data is collected by a Windows service that collects data and adds it to the database once a minute. If the service would also store

Re: [sqlite] Sharing an in-memory database between applications

Since Sqlite caches data in memory you are unlikely to achieve spectacular improvements by having the database memory resident. Perhaps you could investigate performing pre-processing of your data to reduce the time it takes to render your graph. Rob Richardson wrote: Greetings! We are using

Re: [sqlite] Sharing an in-memory database between applications

Rob Richardson wrote: that is much faster than a set of INSERT INTO newtable SELECT * FROM oldtable (or whatever -- you get the idea) statements. The fastest way should be: CREATE TABLE memdb.newtable AS SELECT * FROM oldtable HTH, Gerry -