: [sqlite] DROP INDEX not freeing up memory
Do you have to drop the index? Why not just keep it around, its obviously
useful if you need to create it in the first place right?
Dave Gierok <[EMAIL PROTECTED]> wrote:
It does in fact look like the memory isn't being freed up entirely. I am
pr
: Dave Gierok [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 17, 2007 9:06 AM
To: sqlite-users@sqlite.org
Subject: 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
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] DROP INDEX not freeing up memory
Dave Gierok wrote:
>
> I am running an in-memory db and am using the functionality where
> we override all the OS calls such that we implement our own memory
> management and file IO. Therefore, I am able
is quite a bit of memory in our world.
Any suggestions or explanations?
Thanks,
Dave
-Original Message-
From: Dave Gierok [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 17, 2007 9:06 AM
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] DROP INDEX not freeing up memory
OK, thanks, I'll do
PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] DROP INDEX not freeing up memory
Sqlite is allocating cache memory and reusing it. That is not a bug, it
is a beneficial feature.
Dave Gierok wrote:
Yes, I did try that -- I should have mentioned it. When I create and drop the
index again
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]>
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
the index once costs a lot of memory, and then future
deletions/creations does not change the amount of memory allocated.
-Original Message-
From: John Stanton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 16, 2007 1:56 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] DROP INDEX
Dave Gierok <[EMAIL PROTECTED]> wrote:
>
> I am running an in-memory db and am using the functionality where
> we override all the OS calls such that we implement our own memory
> management and file IO. Therefore, I am able to easily track the
> amount of memory Sqlite is taking up. I have
allocated.
-Original Message-
From: John Stanton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 16, 2007 1:56 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] DROP INDEX not freeing up memory
Dave Gierok wrote:
> (I'm resending this, as I have not seen it posted the first time I s
Hello, I am running an in-memory db and am using the functionality where we
override all the OS calls such that we implement our own memory management and
file IO. Therefore, I am able to easily track the amount of memory Sqlite is
taking up. I have noticed that when I call CREATE INDEX and
11 matches
Mail list logo
