Search methods in ES are "in memory" by default, regardless to mmapfs,
niofs, simplefs etc.
mmapfs uses OS memory optimizations for file reading in addition to
niofs, that is pretty all about it.
The "store" concept
Elasticsearch Platform — Find real-time answers at scale | Elastic is
related to writing data only.
There is a "memory" (RAM only) store option, for keeping volatile data
in the JVM heap. This is useful in the case you only test ES (with
junit/testng, you don't create temp files) or for data from a persistent
source, where recreating by bulk indexing is faster/easier than gateway
storage (which is rarely the case). The "memory" option must not be
confused with search caches for filter/facets which are much more
important for performance.
If you mount a filesystem on a RAM disk and use mmapfs/niofs by pointing
the "path.data" config to it, you can pretty much achieve a better
effect than "memory" store, because OS might optimize I/O and Java might
avoid moving data over the JVM heap.
Jörg
Am 13.07.13 14:43, schrieb oreno:
Thanks Jörg,
I was looking for a solid in memory storage solution. I guess mmapfs
is not the one.
To be honest I don't really understand when it will be good practice
to use explicit 'in memory' storage.
It has no persistence or backup...
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.