4 ms·
Sounds slow, but it depends on the total size of the index. I could see 10K PDFs being big enough to slow things down. The easiest thing to try is setting the J
by rpedela 9y ago
Sounds slow, but it depends on the total size of the index. I could see 10K PDFs being big enough to slow things down. The easiest thing to try is setting the Java heap to half the RAM up to 32GB. The more RAM the better in general. I have also found setting the number of shards to the number of CPU cores to be optimal in many cases, however if a shard is too big (>50GB) then it can start causing other problems. Again the more CPU cores the better in general.
Here are the relevant docs, and don't worry you don't need to know Java to get good performance.
indexing: https://www.elastic.co/guide/en/elasticsearch/reference/current/tune-for-indexing-speed.html https://www.elastic.co/guide/en/elasticsearch/reference/curr...
searching: https://www.elastic.co/guide/en/elasticsearch/reference/current/tune-for-search-speed.html https://www.elastic.co/guide/en/elasticsearch/reference/curr...
disk usage: https://www.elastic.co/guide/en/elasticsearch/reference/current/tune-for-disk-usage.html https://www.elastic.co/guide/en/elasticsearch/reference/curr...
- amelius 9y agoThanks! I'll have a look at that!