Hello Mathias,
I am back again on this story of performance for queries due to the Index
size.
First of all, I wanted to say that in many use-cases the FETCH with the
"gts" key improve a lot of query in our side.
However we still have massive slow queries, for example when we want to
compute a FIND on a specific label on one of our most large application.
The selector query is '~.*{id=42}' and this queries takes more than 70
seconds (server side). The FINDSTATS provides the following result
"{"classes.estimate":14,"gts.estimate":14,"labelnames.estimate":13,"labelvalues.estimate":12,"error.rate":0.008125}".
Even when setting one series name on the selector 'test{id=42}', we still
get series than takes more than 10 seconds to be executed (server side).
I would be to help to improve those queries. What can I look like to start
with?
Le mercredi 11 mars 2020 17:01:50 UTC+1, A. Hébert a écrit :
>
> For sure on a batch of hundred queries an average of 150ms, the best
> resolved in only 28ms, and the worst in 1s
>
> Le mercredi 11 mars 2020 16:52:34 UTC+1, Mathias Herberts a écrit :
>>
>> Did you see an improvement in terms of performance?
>>
>
--
You received this message because you are subscribed to the Google Groups "Warp
10 users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/warp10-users/f28c1af2-e106-4f57-bcdd-e5af2d57b15d%40googlegroups.com.
