[sqlite] Performance test on windows

Hi All, I am a newbie to SQlite, just saw that the performance numbers on www.sqlite.org are not reliable (as per the notce on website, http://www.sqlite.org/speed.html http://www.sqlite.org/speed.html> ) So, I thought of profiling SQlite operations, on linux platform the performance time is quite

RE: [sqlite] Problem using pragmas

Thanks a lot for the reply. You test program did work for me. And apology, cause it was my mistake. There was a corruption in some other unrelated place, That was showing up in sqlite. Thanks, -Saif. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday,

RE: RE: [sqlite] DROP INDEX not freeing up memory

It does in fact look like the memory isn't being freed up entirely. I am properly tracking xMalloc, xRealloc, and xFree. I have a memory database and wrote some test code to loop a few times creating/dropping the same index. The results of that are (numbers are total bytes allocated): 763274

Re: [sqlite] Problem using pragmas

"Saifuddin Rangwala" <[EMAIL PROTECTED]> wrote: > Hi, > > I am trying to configure sqlite-3.3.10 using pragma sql queries, but > it dumps core in sqlite spi. > > What I do is > > 1. sqlite3_open > 2. sqlite3_exec("PRAGMA cach_size = 1000;" > > 2 dumps core. While single steppin

[sqlite] Problem using pragmas

Hi, I am trying to configure sqlite-3.3.10 using pragma sql queries, but it dumps core in sqlite spi. What I do is 1. sqlite3_open 2. sqlite3_exec("PRAGMA cach_size = 1000;" 2 dumps core. While single stepping I found that sqlite3_prepare is called twice inside sqlite3_exec and

Re: [sqlite] DROP INDEX not freeing up memory

I haven't looked at the Sqlite code in detail, but in general it is hard to return memory so memory usage hits a high water mark. You can decide if that is the case just by looking at the Sqlite source and establishing how the memory allocation in your OS and compiler support package works.

RE: [sqlite] DROP INDEX not freeing up memory

OK, thanks, I'll do some more digging and let you know. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 17, 2007 8:30 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] DROP INDEX not freeing up memory Dave Gierok <[EMAIL PROTECTED]> wrote:

Re: [sqlite] Correct use of sqlite3 API (release locks)

Brodie Thiesfield <[EMAIL PROTECTED]> wrote: > Hi, > > I have multiple processes using a single database for both read and > write. I want to ensure that my interpretation of the v3 API spec is > correct. In particular, I want to ensure that all processes lock the > database for the minimum time p

Re: [sqlite] DROP INDEX not freeing up memory

Dave Gierok <[EMAIL PROTECTED]> wrote: > xTruncate is not being called because this is an in-memory database. Memor= > y databases should have memory freed instead I assume? > In-memory databases call sqliteFree() to release their memory. I checked, and this does appear to work. Perhaps the sql

[sqlite] Correct use of sqlite3 API (release locks)

Hi, I have multiple processes using a single database for both read and write. I want to ensure that my interpretation of the v3 API spec is correct. In particular, I want to ensure that all processes lock the database for the minimum time possible and release the lock as soon as they have finishe

RE: [sqlite] DROP INDEX not freeing up memory

xTruncate is not being called because this is an in-memory database. Memory databases should have memory freed instead I assume? Thanks, Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 3:07 PM To: sqlite-users@sqlite.org Subject:

RE: [sqlite] DROP INDEX not freeing up memory

But the docs say VACUUM is supposed to free that memory which it doesn't look like it is doing. -Original Message- From: John Stanton [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 3:41 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] DROP INDEX not freeing up memory Sqlit