7 ms·
Prometheus itself has no scalability at all. Without distributed evaluation they have a brick wall.
by jeffbee 5y ago
Prometheus itself has no scalability at all. Without distributed evaluation they have a brick wall.
- buro9 5y agoThat's what Mimir solves
- deepsun 5y agoHow does it compare to VictoriaMetrics?
- buro9 5y ago100% Prometheus compatible, proven to scale to 1B active series. It's not about comparisons, every tool has it's own place and feature set that may be right for you depending on what you're doing. But if you've reached the end of the road with Prometheus due to scale and you need massive scale and perfect compatibility... Then Mimir stands out.
- halfmatthalfcat 5y agoCan you elaborate? I’ve ran Prometheus at some scale and it’s performed fine.
- lokar 5y agoYou pretty quickly exceed what one instance can handle for memory, cpu or both. At that point you don't have any real good options to scale while maintaining a flat namespace (you need to partition).
- preseinger 5y agoSure? Prometheus scales with a federation model, not a single flat namespace.
- gttalbot 5y agoThis means each new query over a certain size becomes a federation problem, so the friction for trying new things becomes very high above the scale of a single instance. Monitoring as a service has a lot of advantages.
- preseinger 5y agoWell you obviously don't issue metrics queries over arbitrarily large datasets, right? The Prometheus architecture reflects this invariant. You constrain queries against both time and domain boundaries.
- gttalbot 5y agoMonarch can support both ad-hoc and periodic, standing queries of arbitrarily large size, and has the means to spread the computation out over many intermediate mixer and leaf nodes. It does query push-down so that the "expensive" parts of aggregations, joins, etc., can be done in massively parallel fashion at the leaf level. It scales so well that many aggregations are set up and computed for every service across the whole company (CPU, memory usage, error rates, etc.). For basic monitoring you can run a new service in production and go and look at a basic dashboard for it without doing anything else to set up monitoring.
- gttalbot 5y agoAlso, very large ad-hoc queries are supported, with really good user isolation, so that (in general) users don't harm each other.
- xyzzy_plugh 5y agoThat's a choice Prometheus has made, not an invariant. Many scalable systems support arbitrarily large queries as they themselves scale. Prometheus pretty much prevents creating arbitrarily large datasets to begin with, so the point is kind of moot. Requiring query authors to understand the arrangement of their aggregation layer seems like a reasonable idea but is in fact quite ridiculous.
- dilyevsky 5y agoYou can set up dist eval similar to how it was done in borgmon but you gotta do it manually (or maybe write an operator to automate). One of Monarchs core ideas is to do that behind the scenes for you
- jeffbee 5y agoPrometheus' own docs say that distributed evaluation is "deemed infeasible".
- dilyevsky 5y agoThats just like.. you know.. their opinion, man. https://prometheus.io/docs/prometheus/latest/federation/ https://prometheus.io/docs/prometheus/latest/federation/
- bpicolo 5y agoPrometheus federation isn't distributed evaluation. It "federates" from other nodes onto a single node. > Federation allows a Prometheus server to scrape selected time series from another Prometheus server
- dilyevsky 5y agoCollect directly from shard-level prometheus then aggregate using /federate at another level. That’s how thanos also works afaik
- hiptobecubic 5y agoThis still requires the query to fit on a single node at some point unless you're doing multi-level aggregation. Monarch does that. Being able to push expensive, highly-parallelizable aspects of the query down into the leaves is a massive benefit.
- 5y ago
- preseinger 5y agoPrometheus is highly scalable?? What are you talking about??
- dijit 5y agoIt is not. It basically does the opposite of what every scalable system does. To get HA you double you’re number of pollers. To get scale your queries you aggregate them into other prometheii. If this is scalability: everything is scalable.
- preseinger 5y agoI don't understand how the properties you're describing imply that Prometheus isn't scalable. High Availability always requires duplication of effort. Scaling queries always requires sharding and aggregation at some level. I've deployed stock Prometheus at global scale, O(100k) targets, with great success. You have to understand and buy into Prometheus' architectural model, of course.
- dijit 5y agoThe ways in which you can scale Prometheus: you can scale anything. It does not; itself, have highly scalable properties built in. It does not do sharding, it does not do proxying, it does not do batching, it does not do anything that would allow it to run multiple servers and query over multiple servers. Look. I’m not saying that it doesn’t work; but when I read about borgmon and Prometheus: I understood the design goal was intentionally not to solve these hard problems, and instead use them as primitive time series systems that can be deployed with a small footprint basically everywhere (and individually queried). I submit to you, I could also have an influxdb in every server and get the same “scalability”. Difference being that I can actually run a huge influxdb cluster with a dataset that exceeds the capabilities of a single machine.
- preseinger 5y agoIt seems like you're asserting a very specific definition of scalability that excludes Prometheus' scalability model. Scalability is an abstract property of a system that can be achieved in many different ways. It doesn't require any specific model of sharding, batching, query replication, etc. Do you not agree?
- gttalbot 5y agoThis. Any new large query or aggregation in the Borgmon/Prometheus model requires re-solving federation, and continuing maintenance of runtime configuration. That might technically be scalable in that you could do it but you have to maintain it, and pay the labor cost. It's not practical over a certain size or system complexity. It's also friction. You can only do the queries you can afford to set up. That's why Google spent all that money to build Monarch. At the end of the day Monarch is vastly cheaper in person time and resources than manually-configured Borgmon/Prometheus. And there is much less friction in trying new queries, etc.