InstantDB Project
About InstantDB
Project Mail Lists
Short History
Reporting Bugs
Screen Shots
3rd Party Examples
FAQs

Software
Downloads
Documentation
CVS Repositories
Roadmap
License

About Enhydra.org
Who We Are
News, Articles & Events
Getting Involved
Contact Us

Community
Demos
Contributions
Resources
Case Studies
On The Edge! -NEW-
Commercial Vendors

Jason

The following properties can be adjusted to vary the sizes of internal
buffers and caches. The values that follow sets everything to pretty much
minimum values. I haven't tried these out. If they give any problems then
try increasing them slightly. Their meanings are described in:

http://instantdb.enhydra.org/software/documentation/idb3_26b2/props.html

cacheAmount=0
cacheCondition=CACHE_ROWS
systemCacheSize=0
systemCacheCondition=CACHE_ROWS
resultsOnDisk=1
resultsSetCache=CACHE_ROWS
resultsSetCacheAmount=0
rowCacheSize=16
singleRowCount=0
systemRows=0
controlColCacheSize=16
traceLevel=0

In addition, if you want IDB to do garbage collection (3.26 beta 2 only)
then set:

garbageCollectStatements=10
garbageCollectPercent=70

Also, if the data is read only, then set:

transLevel=0

Regards

Pete

--

Peter Hearty                         peter.hearty@lutris.com
Lutris Technologies (UK)        http://www.lutris.com
----- Original Message -----
From: "Jason Amy" <jason@cafesoft.com>
To: <InstantDB@enhydra.org>
Sent: Friday, January 26, 2001 5:06 PM
Subject: InstantDB: InstantDB optimizations


> Hello,
>
> I looked in the mail archives for information regarding my question, but
> could find none, so here goes:
>
> We have an application that runs on a users desktop.  The application
> has 'plugins' which are pieces of code that we can write that seamlessly
> plugin to the main app.  One of these plugins uses InstantDB.  Our
> problem lies in when a particular plugin starts, it runs queries on a
> single InstantDB database.  This database has 10 tables, and all the
> tables combines are .97 megabyte.  None of the tables has more than 7
> columns, and an average of about I'd say 50 rows.  Most data is of type
> char(10) (My SQL syntax may be off, but they're mostly small strings).
> We are noticing a 'jump' in memory usage when the plugin is initialized
> (actually our client has mentioned this memory spike).  Using
> OptimizeIt! I have noticed the largest consumer of memory to be the
> byte[] and char[].  The spike is between 4 and 5 megs (we are trying to
> keep this down to less than 2 megs).  I have changed some of the
> optimization settins in the .prp file (namely the resultsOnDisk to = 1),
> but do not seem to notice much difference.  If someone out there has
> come across this problem, or can enlighten me, it would be greatly
> appreciated!
>
> -Thanks, Jason
>
> --------------------------------------------------------------------------
---
> To unsubscribe from this mailing list, send email to majordomo@enhydra.org
> with the text "unsubscribe instantdb" in the body of the email.
> If you have other questions regarding this mailing list, send email to
> the list admin at owner-instantdb@enhydra.org.
>


-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.