bq. We switched to ByteBuffersDirectory with 7.5, but
I actually didn't see much performance improvements or savings in memory.
Once the indexes are built I don't think there will be much of a
difference. The core problem with RAMDirectory was related to
synchronizations during merges/ file manipu
I doubt using Redis as directory-storage will be very good. I'd expect
it to have much more latency for reads and writes compared to any of
lucene's own directories. And Lucene probably won't like it if another
Lucene-instance changes that database.
It may be interesting as a result-level cache th
Hi Joe,
Elasticsearch used to have an option to run with RAMDirectory but it
was removed long ago:
https://github.com/elastic/elasticsearch/pull/8536.
The recommended approach is to use MMapDirectory and to give
sufficient memory to the filesystem cache so that the most important
data-structures
Greetings,
Has anyone looked into using Redis or some other in-memory cache with Lucene?
It seems that ElasticSearch may do this. Are there advantages to doing this
versus, say, the RAMDirectory class?
Thanks in advance,
J
