I get 2 second response time in average.
Any config / hardware change suggestions for my usecase - low qps rate?
I would say more shards on the same node, but there would be the cache
diminution disadvantage
On Wednesday, February 20, 2013, Walter Underwood wrote:
> In production, you should hav
In production, you should have requests arriving at Solr simultaneously. Those
simultaneous requests will be processed in parallel.
For each query, there are many ways to improve response time. It depends on the
query and the schema.
What query response time are you seeing?
wunder
On Feb 20,
Well, it matters because your single-threaded client is firing one request,
waiting for the response, then firing another. There's no opportunity for
Solr to use more than one thread for queries if there's only a single
thread on a single client ever making requests
Or I misunderstand what you
Yes, i made a one threaded script which sends a querry by a post request to
the shard's url, gets back the response and posts the next querry.
How can it matter?
Manuel
On Wednesday, February 20, 2013, Erick Erickson wrote:
> Silly question perhaps, but are you feeding queries at Solr with a sin
Silly question perhaps, but are you feeding queries at Solr with a single
thread? Because Solr uses multiple threads to search AFAIK.
Best
Erick
On Wed, Feb 20, 2013 at 4:01 AM, Manuel Le Normand <
manuel.lenorm...@gmail.com> wrote:
> More to it, i do see 75 more threads under the process of t
