Looks like the memory usage increased a lot with 10k fields with these two
parameter disabled.
Based on the experiment we have done, looks like ES have abnormal memory
usage and performance degradation when number of fields are large (ie.
10k). Where Solr memory usage and performance remains fo
Thanks!
I have asked Maco to re-test ES with these two parameter disabled.
One more question regard Lucene's capability with large amount of metadata
fields. What is the largest meta data fileds Lucene supports per Index?
What are different strategy to solve the large metadata fields issue? Do
Hi, Mike:
Since both ES and Solr uses Lucene, do you know why we only see big ingest
performance degradation with ES but not Solr?
Are you suggesting that if our customer require large amount of Metadata
field, even Solr won't be able to provide decent performance when ingest
and search are ha
The way we make Solr ingest faster (single document ingest) is by turn off
the engine soft commit and hard commit and use a client to commit the
changes every 10 seconds.
Solr ingest speed remains at 800 docs per second where ES ingest speed
drops in half when we increase the fields (ie. from
Hi, Mark:
We are doing single document ingestion. We did a performance comparison
between Solr and Elastic Search (ES).
The performance for ES degrades dramatically when we increase the metadata
fields where Solr performance remains the same.
The performance is done in very small data set (ie.