Hi Numo and others,
I am very glad to hear the consensus is that there is nothing wrong with
libsqlite3.so.0.8.6.
However the fact is that the 'open' still acquires 16MB of memory.
Immediately Before:
VmSize: 8572 kB
VmLck: 0 kB
VmRSS: 2252 kB
VmData: 484 kB
VmStk: 88 kB
VmExe: 20 kB
VmLib: 6772 kB
VmPTE: 20 kB
Immediately After:
sqlite3_open(sDatabaseFile, &hSqlite) (= SQLITE_OK)
VmSize: 24960 kB
VmLck: 0 kB
VmRSS: 2368 kB
VmData: 16872 kB
VmStk: 88 kB
VmExe: 20 kB
VmLib: 6772 kB
VmPTE: 24 kB
I can't use valgrind as this is a TCP daemon, so I will have to build
some form of simulator to investigate further....
Thanks,
Ben
Nuno Lucas wrote:
On 10/27/06, Ben Clewett <[EMAIL PROTECTED]> wrote:
I am linking to libsqlite3.so.0.8.6. After calling sqlite3_open(...) I
find my programs data memory jumps by 16392 Kb.
This seems a lot. The database I am opening is only 26K in size.
There are many different ways of memory "jump" (like linking with a
lot of dynamic libraries), but one thing is certain: sqlite is not
responsible for that.
I have a similar process opening about 90 times. This obviously
consumes a very large amount of memory, 1.4G with 90 processes.
It's a memory leak in your program, for sure. Run some memory leak
tool (e.g. valgrind).
May I ask if this is what would be expected, and whether there is
anything I can do to lower this loading?
Unless you decided to mess with sqlite internals, it's not expected in
any way.
Thanks for your help,
Ben.
Best regards,
~Nuno Lucas
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
--
Ben Clewett
+44(0)1923 460000
Project Manager
Road Tech Computer Systems Ltd
http://www.roadrunner.uk.com
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
