Re:Building a Full-Text Search App Using Docker and Elastics...
by amelius on Thursday February 01, 2018 @01:08PM
(#16284108)
When I run elastic search out of the box, I've noticed that search is quite slow, on the order of 5 seconds per search, over say 10000 PDF documents (papers), on a single node. Is this normal? And is there an obvious place to look or a (quick) fix which doesn't require me to delve into the ES details too much? (as I'm not a Java person)
[ Parent
| on HN ]
Re:Building a Full-Text Search App Using Docker and Elastics...
by rpedela on Friday February 02, 2018 @12:22AM
(#16288611)
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/curr...
searching: https://www.elastic.co/guide/en/elasticsearch/reference/curr...
disk usage: https://www.elastic.co/guide/en/elasticsearch/reference/curr...