Top all-time · #1861
VictoriaMetrics
Company blog · victoriametrics.com/blogsystemsdataprogramming
VictoriaMetrics is the company blog at victoriametrics.com, writing about systems, data and programming. Since 2019, 40 different Hacker News readers have linked it 102 times, most often “Long-term remote storage for Prometheus”. It is still writing: the last post was on 2026-10-29, and you can follow it by feed.
Too few sampled comments (25) to say how often HN recommends it.?
Why HN links it
HN readers link VictoriaMetrics' blog for Go runtime and performance posts (sync.Mutex, sync.Pool), Prometheus and Mimir benchmarks, and Go release tours. Most comments cite it as support rather than judge it.
Summarised by Claude from a sample of 25 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Monitoring & observability for metrics, logs and traces. Fast, high-performance, open source database solutions from VictoriaMetrics.
Most-linked posts?
- Long-term remote storage for Prometheus8 people · 9 mentions · first linked 2019-05-30
- Grafana Mimir and VictoriaMetrics: performance tests5 people · 6 mentions · first linked 2022-09-09
- Golang Sync Mutex: Normal and Starvation Mode3 people · 3 mentions · first linked 2024-08-08
- How Go Arrays Work and Get Tricky with For-Range3 people · 3 mentions · first linked 2024-08-02
- Go 1.27 Interactive Tour3 people · 3 mentions · first linked 2026-07-31
- VictoriaLogs cluster is available in Open Source2 people · 2 mentions · first linked 2025-06-20
- Go Sync.Pool and the Mechanics Behind It2 people · 2 mentions · first linked 2024-08-24
- How VictoriaLogs Stores Your Logs in a Columnar Layout2 people · 2 mentions · first linked 2026-06-28
- Weak pointers in Go: why they matter now2 people · 2 mentions · first linked 2024-11-29
- The Life of a Metric2 people · 2 mentions · first linked 2026-09-04
What Hacker News says?
> If you have a struct with a simple int field, and you store that somewhere as an *int, the entire struct and anything it points to will be kept alive. While Go allows interior pointers, I don't think what you say is true. runtime.KeepAlive was added exactly to prevent GC from collecting the struct when only a field pointer is stored. Take a look at this blog post, for example: https://victoriametrics.com/blog/go-r…
Comment linking /blog/go-runtime-finalizer-keepalive/
on “Go has added Valgrind support”Submitted Graceful Shutdown in Go: Practical Patterns as a story · 248 points
HN discussionSo, I decided on three locking strategies: No-Lock Optimistic locking Pessimistic locking As a default, the no-lock behavior does exactly what the name implies. Nothing. This is the default because my research shows that for 99% all of this is not an issue and every interaction at this level will slow down the whole application. Aren't the mutexes in the more modern implementations (like Cosmo [0]) & runtimes (like…
Comment linking /blog/go-sync-mutex/
on “SQLite concurrency and why you should care about it”Submitted The Rise of Open Source Time Series Databases as a story · 160 points
HN discussionVictoriaMetrics team member here. Have you had a chance to play with VictoriaLogs? If not, then I highly recommend to test it. Our team is also working on implementing traces in top of Jaeger and VictoriaLogs, see https://victoriametrics.com/blog/dev-note-distributed-tracin...
Comment linking /blog/dev-note-distributed-tracing-with-victorialogs/
on “It's the end of observability as we know it (and I feel fine)”Submitted How Swiss tables work in Go built-in map as a story · 103 points
HN discussionhttps://victoriametrics.com/ would definitely recommend anyone having performance issues with Prometheus to give VictoriaMetrics a try.
Comment linking /
on “All you need is Wide Events, not "Metrics, Logs and Traces"”Submitted Weak pointers in Go: why they matter now as a story · 78 points
HN discussionVictoriaMetrics https://victoriametrics.com/
Comment linking /
on “TimescaleDB vs ClickHouse”Submitted PostgreSQL 19 Interactive Tour as a story · 74 points
HN discussionI'm not sure where you saw that Victoria Metrics uses object storage. It doesn't - it uses block storage and it runs completely fine on HDD, you don't even need SSD/NVMe. There are multiple ways to deal with ingestion floods. Kafka/distributed log is one of them, but it's not the only one. In cluster mode VM is a distributed set of services that scale out independently and buffer at different levels. Resource usage…
Comment linking /blog/mimir-benchmark/
on “I can't recommend Grafana anymore”Submitted VictoriaLogs Practical Ingestion Guide for Message, Time and Streams as a story · 60 points
HN discussionThere is more mature ClickHouse database [1]. This is column-based OLAP database, which provides outstanding query performance (it can scan billions of rows per second per CPU core) and outstanding on-disk data compression (up to 100x if proper table configs are used). ClickHouse also scales horizontally to multiple nodes. Comparing to QuestDB, ClickHouse consistently shows high performance on a wide range of query…
Comment linking /
on “InfluxDB is betting on Rust and Apache Arrow for next-gen data store”Submitted Grafana Mimir and VictoriaMetrics: performance tests as a story · 58 points
HN discussionTime series databases and Kafka are intended for very different workloads. Kafka is used as distributed message queue. I.e. a set of apps produce opaque messages and send them to Kafka queues, while another set of apps consume these messages from Kafka queues. Time series databases are used for storing and querying time series data. There are no Kafka-like queues in time series databases. Every time series has a key…
Comment linking /
on “InfluxDB is betting on Rust and Apache Arrow for next-gen data store”Submitted Golang Sync Mutex: Normal and Starvation Mode as a story · 39 points
HN discussionIt might be the pricing comparison blog post for managed Prometheus solutions here https://victoriametrics.com/blog/managed-prometheus-pricing/
Comment linking /blog/managed-prometheus-pricing/
on “We are still early with the cloud”Submitted Monotonic and wall clock time in the Go time package as a story · 22 points
HN discussionHere you go https://victoriametrics.com/blog/mimir-benchmark/ It is from Sep 2022, it would be great to get newer results.
Comment linking /blog/mimir-benchmark/
on “The Rise of Open Source Time Series Databases”Submitted Go Sync.Cond, the Most Overlooked Sync Mechanism as a story · 13 points
HN discussionIt might be. I've seen the trick pop up a few times: 1. https://puzpuzpuz.dev/thread-local-state-in-go-huh 2. https://victoriametrics.com/blog/go-sync-pool/ It's probably too complex for the Otel SDK, but I might give it a spin in my experimental tracing repo.
Comment linking /blog/go-sync-pool/
on “OpenTelemetry for Go: Measuring overhead costs”Submitted Go 1.27 Interactive Tour as a story · 10 points
HN discussion> had not heard of anyone actually using a spinlock in production code Go stdlib sync.Mutex uses spins: https://victoriametrics.com/blog/go-sync-mutex / https://archive.vn/BIb7F
Comment linking /blog/go-sync-mutex
on “Optimizing a Spin-Lock”Submitted Comparing Elasticsearch, Tempo, ClickHouse and VictoriaLogs in Tracing Benchmark as a story · 6 points
HN discussion> I don't see why did you label Aliaksandr Valialkin, the author, an "expert". I mean, he's no dummy but what exactly makes him an expert on optimizing Go code? https://victoriametrics.com/team/ - Let's see. Author of multiple performance-optimized libraries with a masters degree in computer software engineering and a background in highly scalable systems (as needed for adtech). Sounds pretty much like an expert for…
Comment linking /team/
on “Fivefold Slower Compared to Go? Optimizing Rust's Protobuf Decoding Performance”Submitted Logs Ingestion Benchmark: Loki, Elasticsearch, VictoriaLogs and ClickHouse as a story · 5 points
HN discussionOodle is a fully managed, supports high availability, so was comparing against the cluster mode of victoria metrics cloud offering. RE: Victoria Metrics Pricing: Pls see https://victoriametrics.com/products/cloud/ . The pricing that you are referring doesn't seem public, looks like you've to sign up to see that pricing. $190/month is a single node pricing. For any real use cases, you need HA and victoria metrics ent…
Comment linking /products/cloud/
on “Show HN: Oodle – serverless, fully-managed, drop-in replacement for Prometheus”Submitted Container CPU requests and limits explained with GOMAXPROCS tuning as a story · 5 points
HN discussionOodle is a fully managed offering. Curious why you think Victoria Metrics Cloud is still cheaper. https://victoriametrics.com/products/cloud/ This translates to about $5.2 per 1k metrics, Oodle is $1 per 1k metrics! Am I missing something?
Comment linking /products/cloud/
on “Show HN: Oodle – serverless, fully-managed, drop-in replacement for Prometheus”Submitted VictoriaLogs vs. Loki, Elasticsearch, OpenSearch, SigNoz and ClickStack as a story · 4 points
HN discussion
