Make your own free website on Tripod.com

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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

InstantDB: Usage of memory by indexes


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.