yes, that solr queries continue to run the query on the solr server even
after a connection is broken was my understanding and concern as well
I was hoping I had overlooked or missed something in Solr or Tomcat
documentation that might do the job
it is unfortunate
if anyone else can think of som
solr-user [solr-u...@hotmail.com] wrote:
> while we have optimized our queries for an average 50ms response time,
> we do occasionally see some that can run between 10 and 100 seconds.
That sounds suspicious. Response times so far from your average indicates that
there is special processing going
millions of documents per shard, with a number of shards
~40gb index folder size
12gb of heap on a 16gb machine (this old Solr doesnt use O/S mem space like
4.x does)
servers are hosted internally, and are powerful
understood. as mentioned, we tuned the bulk of our queries to run very
quickly (50
How big is the index (document count, gigabytes)?
How much RAM is on the servers?
How big is your Java heap?
How are the servers hosted? AWS?
Long queries are often caused by long-tail queries fetched from disk. There are
several ways to speed these up, but they all use RAM or SSD.
wunder
Wal
