<localCache subIndex="__default__" connection="memory://" />
brought the query time to as low as: 280*secs* for the first query, and 280msec for the second (which is exactly the performance expected from a file index). Still, this is far from acceptable. is there anything i can do to improve the jdbc-dir throughput? i´ve seem an incredible number of queries fired against the DB when initially caching the index. maybe some more buffers here and there? already tried with FileBuffers, but with no significant effect, but a OOM when being too generous
In the file based local cache, the first query will need to download (most of the) index to the file system. Then, only delta changes are applied to the database, and search / reads only occur against the local one.
Synchronization on first use is in acceptable Range (from one sec to 20 secs depending on the actual change to be synced of course), and query performance as fasst as simple file directory. Inserting is acceptable as well, just reindexing is still expensive, but that is probably inevitable.
The above FileEntry setting improved throughput by roughly 200%.
Again: right for ME, not necessarily for anyone else, considering different usage patterns, memory requirements etc.
Another option promising a good performance for my usecase seems to be a file-directory on a Distributed Block Device. Is there a good reason to not do that?
Thanks to Shay for helping out.
PS: apart from thisdifficulty, i love compass for its ease of use and (almost) proper documentation. Kudos to Shay!