On 6/7/2018 12:10 PM, Moenieb Davids wrote: > Challenges: > When performing full text searches without concurrently executing updates, > solr seems to be doing well. Running updates also does okish given the > nature of the transaction. However, when I run search and updates > simultaneously, performance drops quite significantly. I have played with > field properties, analyzers, tokenizers, shafting sizes etc.
I have absolutely no idea what a shafting size is. If I google for it, the only relevant thing that comes up is your message on this list. Doing updates at the same time as queries will always have an impact on query performance. But if that impact is very significant, then it sounds like the machine doesn't have enough memory to allow the OS to effectively cache the index data. When updates are made, all the data that is written will end up in the disk cache, and if the cache is as big as can get already, it will push older data out of the cache. Disks are very slow compared to memory, so if the index data required to complete a query must be read from the disk, performance is adversely affected. A page discussing OS disk cache requirements: https://wiki.apache.org/solr/SolrPerformanceProblems#RAM Thanks, Shawn
