[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
InstantDB: Usage of memory by indexes
- To: instantdb@enhydra.org
- Subject: InstantDB: Usage of memory by indexes
- From: Jack Orenstein <jao@mediaone.net>
- Date: Sun, 18 Mar 2001 07:34:10 -0500
- Reply-To: instantDB@enhydra.org
- Sender: owner-instantDB@enhydra.org
On March 15 you said the following, responding to Bhavna Khera:
InstantDB can take up a lot of memory. Indexes are held entirely
in memory for example.
Can you expand on this? Are you saying that an index for a large table
is read in its entirety the first time any part of it is needed? Or that
parts
of it are read on demand and then remain in memory? Do they stay for
the duration of the current transaction? JVM?
Jack Orenstein
-----------------------------------------------------------------------------
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.
|
- Prev by Date: Re: InstantDB: Working together with jbuilder JDBC Eplorer
- Next by Date: InstantDB: Hi,newbie here
- Prev by thread: InstantDB: ETA on open source
- Next by thread: InstantDB: Hi,newbie here
- Index(es):
