Aliaksandr Valialkin

FYI, the `debug` mode is available in `vmalert` starting from the commit 0ead64b6cfe7eed31ccfdf5c0aab836c652b8c4e . The debug mode can be enabled at alerting rule by specifying `debug: true` option. See [these...

> How do you mean with "easier to manage"? The specific backends? Can you give an example? For instance, [VictoriaMetrics](https://github.com/VictoriaMetrics/VictoriaMetrics) consists of a single self-contained binary, which works out of...

> One thing that I have been dwelling on is how to handle the geographical metadata. These are currently treated separately by LTSS to make use of the PostGIS extension...

VictoriaMetrics usually needs much lower compute resources - RAM, CPU, disk space, disk IO - compared to InfluxDB on the same workload. See [these case studies](https://docs.victoriametrics.com/CaseStudies.html) and [these benchmarks](https://docs.victoriametrics.com/Articles.html#benchmarks). This...

Unfortunately this isn't possible by design, since this may result in out of memory errors when a lot of items are added to the cache and none are deleted.

Could you elaborate the purpose of the feature? The usual workflow for the cache is: ```go v := c.Get(nil, k) if len(v) == 0 { v = createValue() c.Set(k, v)...

I think it is better limiting the size of the cache, so it could be saved to disk in reasonable time. I see little sense in partially saved cache.

While this is technically possible, this is out of scope for the `fastcache`. I'd recommend forking it and adding support for disk-based cache on top of mmap'ed files.

Because `bytes.Equal` is implemented in the same way - see https://cs.opensource.google/go/go/+/refs/tags/go1.17:src/bytes/bytes.go;l=18 : ```go func Equal(a, b []byte) bool { return string(a) == string(b) } ``` Go compiler automatically optimizes such...

int in Go is equivalent to int64 on 64-bit architectures. As for 32-bit archs, they usually cannot address more than 2^32 bytes in process memory.