From c2ca6cb84d8f6b71a046c4338dd47e828e523cda Mon Sep 17 00:00:00 2001 From: hagen1778 <roman@victoriametrics.com> Date: Tue, 12 Dec 2023 10:28:11 +0100 Subject: [PATCH] docs: fix formatting after a list in CHANGELOG.md Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit 1e02efd51120900d0439e53b4f6154a6f61c7e65) --- docs/CHANGELOG.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md index 2097f29e2f..51aff12e3a 100644 --- a/docs/CHANGELOG.md +++ b/docs/CHANGELOG.md @@ -101,6 +101,7 @@ Released at 2023-11-15 - [`max_over_time`](https://docs.victoriametrics.com/MetricsQL.html#max_over_time) - [`min_over_time`](https://docs.victoriametrics.com/MetricsQL.html#min_over_time) - [`rate`](https://docs.victoriametrics.com/MetricsQL.html#rate) + The optimization is enabled when these functions contain lookbehind window in square brackets bigger or equal to `6h` (the threshold can be changed via `-search.minWindowForInstantRollupOptimization` command-line flag). The optimization improves performance for SLO/SLI-like queries such as `avg_over_time(up[30d])` or `sum(rate(http_request_errors_total[3d])) / sum(rate(http_requests_total[3d]))`, which can be generated by [sloth](https://github.com/slok/sloth) or similar projects. * FEATURE: `vmselect`: improve query performance on systems with big number of CPU cores (`>=32`). Add `-search.maxWorkersPerQuery` command-line flag, which can be used for fine-tuning query performance on systems with big number of CPU cores. See [this pull request](https://github.com/VictoriaMetrics/VictoriaMetrics/pull/5195). * FEATURE: `vmselect`: expose `vm_memory_intensive_queries_total` counter metric which gets increased each time `-search.logQueryMemoryUsage` memory limit is exceeded by a query. This metric should help to identify expensive and heavy queries without inspecting the logs.