Im using H2 to implment a persistent key-value store where the keys are strings and the values are serialised objects. The DB is extremely large and the reads will be more or less randomly distributed accross the keys. So caching of the data pages may not provide much of a perfomance boost but caching the index seems to be crucial.
Is there a formula or method for determining how much cache to allocate to be able to keep the index in memory? Also, I seem to recall seeing in the old doco a configuration setting for influecing H2 to give more or less preference to index files in the cache, but I can't seem to find it now. Or did I dream this? Thanks, Paul -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
