mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-12-19 07:01:02 +01:00
cad236003b
Previously the query could return incorrect results, since the query timestamp was updated with every Query.Clone() call during iterative search for the time range with up to limit=N rows. While at it, optimize queries, which find low number of matching logs, while spend a lot of CPU time for searching across big number of logs. The optimization reduces the upper bound of the time range to search if the current time range contains zero matching rows. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6785 |
||
---|---|---|
.. | ||
buffered_writer.go | ||
hits_response.qtpl | ||
hits_response.qtpl.go | ||
logsql.go | ||
logsql.qtpl | ||
logsql.qtpl.go | ||
query_response.qtpl | ||
query_response.qtpl.go | ||
stats_query_range_response.qtpl | ||
stats_query_range_response.qtpl.go | ||
stats_query_response.qtpl | ||
stats_query_response.qtpl.go |