Joe
Without any figures to go on (number of tables, indexes, caching properties
etc.) it's difficult to give any specific advice. The default "sample.prp"
supplied with InstantDB will normally limit the amount of table caching that
goes on. However, you should bear in mind that indexes are always 100%
cached and will generally grow linearly with the size of your tables.
It's also worth looking into whether sufficient garbage collection is taking
place. I'm not really an expert in this area, but the occasional call to the
garbage collector during idle moments might help to reduce your overall
memory footprint.
Regards
Peter Hearty
Lutris Technologies UK Ltd.
-----Original Message-----
From: Joe Patti <jpatti@smtp.gateway.net>
To: instantdb@enhydra.org <instantdb@enhydra.org>
Date: 19 July 2000 20:02
Subject: InstantDB: Getting increasing number of out of memory errors with
more tables
>Hi,
> as I am developing a database with IDB, my application is getting out
>of memory errors, that I wasn't getting before I had to add additional
>tables to my database. I have set resultsOnDisk=1 in the properties and
>removed most of the tracking and other things to try and limit memory
>usage. Is there anything else that I can do to try and lower my memory
>footprint.
>
>
>Thanks,
>Joe
>
>---------------------------------------------------------------------------
--
>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.
|