Re: [sqlite] Repost: Accessing a DB while copying it causes Windows to eat virtual memory

ers-boun...@sqlite.org > [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Mark Spiegel > Sent: Wednesday, July 08, 2009 2:02 PM > To: General Discussion of SQLite Database > Subject: Re: [sqlite] Repost: Accessing a DB while copying it causes Windows > to eat virtual memory >

Re: [sqlite] Repost: Accessing a DB while copying it causes Windows to eat virtual memory

Hello again, Copying the database with Explorer and accessing it via sqlite is just a contrived example that exhibits the same problem I'm having in my application. The app does make a copy of the DB, but it has app-layer locking that will prevent modifications unless someone decides to start fidd

Re: [sqlite] Repost: Accessing a DB while copying it causes Windows to eat virtual memory

On Tue, Jul 7, 2009 at 1:10 PM, Mark Spiegel wrote: > This should give you a picture of who is opening the file and with what > flags.  In particular, how is your SQLite app and Explorer opening the file? Thanks for the pointer to Filemon; I'm always happy to learn about a new tool. Apparently it

Re: [sqlite] Repost: Accessing a DB while copying it causes Windows to eat virtual memory

the following error: Errror 0x80070021: The process cannot access the file because another process has locked a portion of the file. On Tue, Jul 7, 2009 at 1:03 PM, John Stanton wrote: > You should synchronize your backup (copy).  Try surrounding it with an > exclusive transaction. > >

[sqlite] Repost: Accessing a DB while copying it causes Windows to eat virtual memory

Sorry for the repost, but the original thread was hijacked by another list user. This is a serious problem IMHO; it looks like the DB can't be backed-up without rendering the machine unusable if a query hits it while a copy is in progress. Hello, In the course of copying a largish (20 GB) databas

[sqlite] Accessing a DB while copying it causes Windows to eat virtual memory

Hello, In the course of copying a largish (20 GB) database file while accessing it via sqlite3, the machine became very unresponsive. I opened task manager and found that the system was using a huge amount of virtual memory, causing it to thrash. Per-process memory usage looked normal and did not

[sqlite] Reducing memory usage when reading a blob

Hello, I'm cooking up some blob reading code based on the following example -> http://www.sqlite.org/cvstrac/wiki?p=BlobExample The author prepares a statement and reads the blob value in the following manner -> *if*( rc==SQLITE_ROW ){** *pnBlob = sqlite3_column_bytes

Re: [sqlite] Performance problems potentially related to index scalability

On 2/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: "Stan Bielski" <[EMAIL PROTECTED]> wrote: > > Anyone care to take a guess what's going on here? The problem is that you are thrashing. The working set on the database file is exceeding the amount of memo

Re: [sqlite] Performance problems potentially related to index scalability

On 2/8/07, Griggs, Donald <[EMAIL PROTECTED]> wrote: Regarding: "...Next, I add in an index on [one] of my numeric columns. ... This is where the problem comes in." You may already know this, but if you can tolerate waiting until the loads are complete before adding the index, the total perfor

[sqlite] Performance problems potentially related to index scalability

Greetings, I'm running into some performance problems with my insert operations using sqlite 3.35. OS is linux with a 2.69 kernel using an out-of-box ext3 file system. My schema consists of a single table with 12 columns with a numeric affinity and 5 columns with text affinity. The table has a p