Skip to content

D
docs
Commit 1a3089c1 authored by Stuart Nelson's avatar Stuart Nelson
Browse files
Options

Update wording in comparison.md

parent b6bab9d4
Hide whitespace changes
Inline Side-by-side
Showing with 4 additions and 8 deletions
content/docs/introduction/comparison.md
View file @ 1a3089c1
...@@ -9,7 +9,7 @@ sort_rank: 4 ...@@ -9,7 +9,7 @@ sort_rank: 4
### Scope ### Scope
[Graphite](http://graphite.readthedocs.org/en/latest/) focusses on being a [Graphite](http://graphite.readthedocs.org/en/latest/) focuses on being a
passive time series database with a query language and graphing features. Any passive time series database with a query language and graphing features. Any
other concerns are addressed by external components. other concerns are addressed by external components.
...@@ -35,7 +35,7 @@ instance as a dimension and being able to drill down into individual ...@@ -35,7 +35,7 @@ instance as a dimension and being able to drill down into individual
problematic ones. problematic ones.
As an example, storing the number of HTTP requests to API servers with the As an example, storing the number of HTTP requests to API servers with the
response code `500` and the method `POST` to the `/tracks` controller would response code `500` and the method `POST` to the `/tracks` endpoint would
commonly be encoded like this in Graphite/StatsD: commonly be encoded like this in Graphite/StatsD:
``` ```
...@@ -71,9 +71,6 @@ unable to consider it as an alternative at the time. Still, there are ...@@ -71,9 +71,6 @@ unable to consider it as an alternative at the time. Still, there are
significant differences between Prometheus and InfluxDB, and both systems are significant differences between Prometheus and InfluxDB, and both systems are
geared towards slightly different use cases. geared towards slightly different use cases.
The comparisons below attempt to help you choose the right system for your use
case and taste:
### Scope ### Scope
The same scope differences as in the case of The same scope differences as in the case of
...@@ -98,13 +95,12 @@ disk storage in InfluxDB than in Prometheus** due to this different data model. ...@@ -98,13 +95,12 @@ disk storage in InfluxDB than in Prometheus** due to this different data model.
If you are only interested in tracking the development of existing named If you are only interested in tracking the development of existing named
time series (for example, the cumulative count of HTTP requests with the method time series (for example, the cumulative count of HTTP requests with the method
`POST` and the handler `/api/tracks` on the instance `POST` to the `/api/tracks` endpoint on the instance
`http://1.2.3.4:12345/metrics`), Prometheus will require much less storage `http://1.2.3.4:12345/metrics`), Prometheus will require much less storage
space than InfluxDB. Further, Prometheus indexes all time series dimensions for space than InfluxDB. Further, Prometheus indexes all time series dimensions for
efficient filtering, while InfluxDB currently only indexes tables by row efficient filtering, while InfluxDB currently only indexes tables by row
timestamps (issue to track adding column indexes: timestamps (issue to track adding column indexes:
https://github.com/influxdb/influxdb/issues/582). Thus, I would expect https://github.com/influxdb/influxdb/issues/582).
Prometheus to be more efficient at filtering data.
Still, InfluxDB is better geared towards the following use cases: Still, InfluxDB is better geared towards the following use cases:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment

Technounit-GROUP 2023