for the
query result cache.
We already have a custom implementation in which we check our redis cache for
queries before they are sent to our aggregators which runs at 30% hit rate.
Kind Regards,
James Bodkin
On 17/06/2020, 16:21, "Michael Gibney" wrote:
To expand a bit on
"true" regardless of
whether indexed is true or false?
Kind Regards,
James Bodkin
On 17/06/2020, 14:02, "Michael Gibney" wrote:
facet.method=enum works by executing a query (against indexed values)
for each indexed value in a given field (which, for indexed=false, i
arts of the index to be read. In this case,
probably just facet on all the fields you care about. I'd add sorting too
if you sort on different fields.
The *:* query without facets or sorting does virtually nothing due to some
special handling...
On Tue, Jun 16, 2020, 10:4
got to query 4, as I
thought this would replicate the actions of the newSeacher.
Unfortunately we can't use the autowarm count that is available as part of the
filterCache/filterCache due to the custom deployment mechanism we use to update
our index.
Kind Regards,
James Bodkin
On 16/06/202
s by using a rolling deployment
in Kubernetes.
Kind Regards,
James Bodkin
On 12/06/2020, 18:58, "Erick Erickson" wrote:
I question whether fiterCache has anything to do with it, I suspect what’s
really happening is that first time you’re reading the relevant bits from disk
in
We've run the performance test after changing the fields to be of the type
string. We're seeing improved performance, especially after the first time the
query has run. The first run is taking around 1-2 seconds rather than 6-8
seconds and when the filter cache is present, the response time is a
hange the field type to a string, as our queries are always
looking for a specific value (and not intervals/ranges) and rerun our load test.
Kind Regards,
James Bodkin
On 11/06/2020, 14:49, "Erick Erickson" wrote:
There’s a lot of confusion about using points-based fields
he underlying Google
Cloud Virtual Machine in our load test environment has 6 vCPUs, 32G RAM and
100GB SSD.
Would anyone be able to point me in a direction to either improve the
performance or understand the current performance is expected?
Kind Regards,
James Bodkin
