I'd examine the filter queries used to see whether they make sense as well.
You really have to re-tune after you start getting real user queries though
as anything you generate won't reflect reality. I'd start _much_ smaller, 512
or 1024 and work _up_ with real data.
Raising the document cache lim
Hi,
The real production requests will not be randomly generated, and a lot of
requests will be repeated. I think the performance will be better due to the
repeated requests. In addition, I am sure the configuration will need to be
adjusted once the application is in production.
For the time being
It's actually unlikely that increasing the documentCache will
help materially. It's primarily so various components won't
have to fetch the documents off disk for a _single_ request.
I've heard some anecdotal evidence that it helps in some situations,
but that's been rare in my experience.
Your fi
On 7/9/2015 9:48 AM, wwang525 wrote:
> I did a load test with a total of 800 requests (at 40 concurrent requests
> per second) to be executed against Solr index with 14 M records. Performance
> was good (< 1 second) especially after a short period of time of the test.
> BTW, the second round of loa
