So far no answer from Sofiya. That's fair enough: My suggestions might
have seemed random. Let me try to qualify them a bit.
What we have to work with is the redacted query
q=&fl=&start=0&sort=&fq=&rows=24&version=2.2&wt=json
and an earlier mention that sorting was complex.
My suggestions were t
On Wed, 2018-10-31 at 13:42 +0200, Sofiya Strochyk wrote:
> q=&fl=&start=0&sort= expression>&fq=&rows=24&version=2.2&wt=json
Not much to see here, perhaps because you are not allowed to share it?
Maybe we can try and isolate the cause? Could you try different runs,
where you change different comp
The logfiles on your servers should be verbose enough to indicate what
machines are handling which parts of the request.
Yes, generally i see the following entries in logs:
1.
df=_text_&distrib=false&fl=_id&fl=score&shards.purpose=4&start=0&fsv=true&sort=fq=&shard.url=&rows=24&version=2&q=&NO
Hi Ere,
Thanks for your advice! I'm aware of the performance problems with deep
paging and unfortunately it is not the case here, as the rows number is
always 24 and next pages are hardly ever requested from what i see in
the logs.
On 29.10.18 11:19, Ere Maijala wrote:
Hi Sofiya,
You've a
