Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
valyala
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
35 ms
·
451.
▲
by
valyala
7y ago
It is easy to implement RAID1-like replication in VictoriaMetrics: just set up independent VictoriaMetrics instances (single-node or clusters) and replicate all the incoming data simultaneously to these instances. This can be done either vi
452.
▲
by
valyala
7y ago
According to Cortex docs [1], a single-process Cortex isn't production ready. It is intended for development and testing only. [1] https://cortexmetrics.io/docs/configuration/single-process-c...
453.
▲
by
valyala
7y ago
VictoriaMetrics FAQ contains comparisons to Cortex [1] and Thanos [2]. [1] https://github.com/VictoriaMetrics/VictoriaMetrics/wiki/FAQ#... [2] https://github.com/VictoriaMetrics/Victoria
454.
▲
by
valyala
7y ago
It is more like RAID0. VictoriaMetrics shards time series among available vmstorage nodes. I.e. each vmstorage node contains a part of data stored in the cluster. This is usually named shared nothing architecture [1]. As for data replicatio
455.
▲
Vmagent – fast and flexible metrics collector and router
(github.com)
1 points
by
valyala
7y ago
|
0 comments
456.
▲
Better Prometheus Rate() Function with VictoriaMetrics
(percona.com)
4 points
by
valyala
7y ago
|
0 comments
457.
▲
by
valyala
7y ago
There is a TSDB solution if you don't want getting a little dirty - VictoriaMetrics [1]. It is built on the same principles as ClickHouse [2]. [1] https://github.com/VictoriaMetrics/VictoriaMetrics/blob/m
458.
▲
Show HN: Time series database by the creator of fasthttp Go package
(github.com)
6 points
by
valyala
7y ago
|
0 comments
459.
▲
Billy: VictoriaMetrics deals with more than 500B rows
(medium.com)
3 points
by
valyala
7y ago
|
0 comments
460.
▲
by
valyala
7y ago
Ingestion rate of 1K metrics per second can be handled by any solution on low-end hardware. I believe even ancient Raspberry PI would feel comfortable with such a load :) VictoriaMetrics scales to 50M+ metrics per second on a single server
461.
▲
by
valyala
7y ago
VictoriaMetrics author here. I like the post, since it is cleanly written and it isn't biased to certain solution. I'd recommend readers trying all the mentioned solutions - Thanos, Cortex, M3DB and VictoriaMetrics and then choosi
462.
▲
by
valyala
7y ago
Btw, it should be easy adding fsync to ClickHouse. For instance VictoriaMetrics uses similar file format as ClickHouse, and it issues proper fsyncs at least every second, so it may lose only the last second of data on unclean shutdown such
463.
▲
by
valyala
7y ago
VictoriaMetrics core developer here. The performance numbers from ClickHouse running on Intel NUC are impressive! We are going to publish VictoriaMetrics performance numbers for the original Billy benchmark from ScyllaDB [1] running on the
464.
▲
by
valyala
7y ago
Thanks for the warm response! > Honestly, @valyala should just create a metrics collector and then I wouldn't have to deal with the "we know better" attitude from some Prometheus contributors We didn't want going this
465.
▲
by
valyala
7y ago
To be fair, VictoriaMetrics also contributes to Prometheus ecosystem by providing open source cost-effective remote storage for Prometheus, which is easy to setup and operate. Additional contributions to Prometheus ecosystem include: * Fili
466.
▲
by
valyala
7y ago
Great news! I hope this isn't a sarcasm :)
467.
▲
by
valyala
7y ago
> You continue to claim that VictoriaMetrics is backwards-compatible with Prometheus and only include a side-note that it actually is not in all cases * There are a few controversial cases where VictoriaMetrics' implementation for P
468.
▲
by
valyala
7y ago
Yet another case of "fair" competition from Prometheus and Thanos devs [1]: * Prometheus users proposed extending `/api/v1/label/.../values` API [2], which has been already implemented in VictoriaMetrics.
469.
▲
by
valyala
7y ago
I'm trying hard to write polite comments, which could help users finding the solution for their issues. My comments could be harsh only in response to misleading posts about VictoriaMetrics [1]. [1] https://www.robustpercept
470.
▲
by
valyala
7y ago
Another case of unfair competition is the article [1] published by Prometheus author, where he claims VictoriaMetrics doesn't compress random data well. I hope Prometheus author knows information theory [2] and was aware that random da
471.
▲
by
valyala
7y ago
An additional case of unfair competition was at PromCon 2019. There was a talk named `Remote storage wars` from Adidas at the conference [1]. Various remote storage solutions for Prometheus were compared in the talk for use cases specific t
472.
▲
Are Prometheus and Thanos developers against fair competition?
8 points
by
valyala
7y ago
|
17 comments
473.
▲
Prometheus storage: tech terms for humans
(medium.com)
2 points
by
valyala
7y ago
|
0 comments
474.
▲
Evaluating performance and correctness: VictoriaMetrics response
(medium.com)
3 points
by
valyala
7y ago
|
0 comments
475.
▲
by
valyala
7y ago
I hope TimescaleDB compression level will eventually reach VictoriaMetrics compression level for typical time series data :) [1] [1] https://medium.com/@valyala/measuring-vertical-scalability-f...
476.
▲
by
valyala
7y ago
There is VictoriaMetrics, which is also written in Go and shows much higher performance numbers than InfluxDB, especially on high cardinality data. See [1], [2] and [3]. [1] https://medium.com/@valyala/measuring-vertica
477.
▲
by
valyala
7y ago
Another viable player that took the path similar to M3DB is VictoriaMetrics [1]. This allowed implementing various features [2] and optimizations [3] without the need to negotiate their integration into upstream Prometheus. Such negotiation
478.
▲
Speeding up backups for big time series databases
(medium.com)
4 points
by
valyala
7y ago
|
0 comments
479.
▲
by
valyala
7y ago
This is great news! We at VictoriaMetrics [1] are happy that TimescaleDB eventually addressed high disk usage issue and implemented type-aware column-based compression. This should improve its' position and performance in TSBS benchmar
480.
▲
by
valyala
7y ago
VictoriaMetrics cluster has slightly lower performance numbers comparing to single-node version because of network overhead for RPC communications between cluster components. Some numbers for VictoriaMetrics cluster: - Ingestion speed is mo
More ›