You need to get help from Dr Hipp for that. I believe he has a special cut down version of Sqlite which omits the compiler and has a special way of storing prepared SQL statements. It is obviously intended for small footprint embedded applications with a specific functionality.

Kalyani Tummala wrote:
Hi John,
Thanks for your help. I have another doubt? If I turn off the sql
compiler, should I have to fix my insert,delete,select,update
operations? My operations are almost fixed in nature. Can you tell me
how exactly I do this?


-----Original Message-----
From: John Stanton [mailto:[EMAIL PROTECTED] Sent: Thursday, November 30, 2006 11:26 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Query on database operations.

You might find that a version of Sqlite which omits the compiler might fit your application. You get a smaller footprint, but at the cost of having to use pre-compiled SQL, which means that you cannot dynamically create SQL.

Kalyani Tummala wrote:

Hi,

This mail is a bit lengthy. I thank you in advance for your patience

and

help:-).



Here we go......



I need to port sqlite to a platform where the RAM size is too small
about 512kb.  For that I need to tune sqlite to make its footprint,

heap

and stack memory as small as possible.


As said in the documentation on sqlite.org, I could get the least
possible footprint of 170KB with all the optional features turned off.



My Analysis of heap and stack usage is as follows.



Stack memory is consistent about 9-10K



Heap memory is highly variant on size and number of records. I tried
modifying the page size(SQLITE_DEFAULT_PAGE_SIZE and
SQLITE_MAX_PAGE_SIZE ) in pager.h from 512 to 2048 but found no
reduction in heap size.


With indexes on every column(searched), the following is the heap size
for different database operations on a database with 100 records and 6
tables with an avg of 10 to 15 fields each.



Operation                                            MAX Heap
Average Heap(Bytes)

insertion

85939

24166

deletion

397834

76541

Selection of all records

246973

79075

Update of all records

249808

196334



It seems quite a huge heap consumption. Are these numbers as expected?
Is there a way that I can reduce these numbers in the range of 40-50kB
by any means (including accessing pattern).


I would like to know the reason for high heap consumption for deletion
operation.


Thanks in advance.

Kalyani





**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
[EMAIL PROTECTED]
**********************************************************************





------------------------------------------------------------------------
-----
To unsubscribe, send email to [EMAIL PROTECTED]
------------------------------------------------------------------------
-----


-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------



-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to