John, thanks a lot for your excellent reply.
Especially, I think this sentence is very convincing,
> "Well, you _can_ be a lot better since you know what
you're
> doing. You can also be a _lot_ worse when you get it
wrong.
With such a high risk, probably I should try other
tricks to improve t
Kan Deng wrote:
1. Performance.
Since all the cached disk data resides outside JVM
heap space, the access efficiency from Java object to
those cached data cannot be too high.
True, but you need to compare the relative speeds. If data has to be
pulled from a file, then you're talking se
Thanks, Otis.
Also appreciate your wonderful book, "Lucene in
Action". The book is so well written that it makes me
very curious about the low level design of the system,
in addition to how to use it.
Back the cache problem, I agree that the native OS
file system can do most of the job for me.
Kan,
Some (all?) of what you described will typically be handled for you by the file
system. Yes, the JVM would blow up with a OOM error if the index is too big to
fit in RAM.
Otis
- Original Message
From: Kan Deng <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Cc: Kan Deng <[EM
