Nikolay

> Hi [@f41gh7](https://github.com/f41gh7) , Did you have a chance to take a look at the Churn rate? Hello, sorry for delay. Churn rate looks good to me. It doesn't have...

@vskovpan-harmonicinc , sorry for delay, I think the following feature should help for your case https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6014 As soon as it'll be implemented, background merge speed could be limited. It should...

The bugfix was included into [v1.107.0](https://docs.victoriametrics.com/changelog/#v11070), [v1.102.8](https://docs.victoriametrics.com/changelog/#v11028) and [v1.97.13](https://docs.victoriametrics.com/changelog/#v19713).

I think, it's better to change influx parsing API. Instead of having `string` - immutable object, it's better to pass `[]byte` to the parser. It allows to mutate []byte in-place...

The enhancement was included into [v1.132.0](https://docs.victoriametrics.com/changelog/#v11320)

Possible solution could be to introduce new RPC call for vmselect->vmstorage query request. New RPC must not use streaming ZSTD compression and instead apply per-block ZSTD compression. In addition, it...

> [@f41gh7](https://github.com/f41gh7) Just to check, is there information on what can be done about this higher request latency, such as by increasing the top level vmselects timeout above the 30s...

@rtm0 WDYT of making `dateMetricIDCache` persistent?

The bugfix was included into [v1.132.0](https://docs.victoriametrics.com/changelog/#v11320)

If client could open a lot of network connections, it could overload vmauth and perform DDoS in any way. I think, it's better to delegate such functional to the dedicated...