Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Updated link in OSS optimize doc

pull/1983/head
Scott Anderson 2020-12-16 13:32:37 -07:00 committed by GitHub
parent 94ca8db7ba
commit 37a1f7ecb2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/influxdb/v2.0/query-data/optimize-queries.md
View File

@ -74,7 +74,7 @@ We're continually optimizing Flux and this list may not represent its current st
## Balance time range and data precision
To ensure queries are performant, balance the time range and the precision of your data.
For example, if you query data stored every second and request six months worth of data,
results would include ≈15.5 million points per series. Depending on the number of series returned after `filter()`([cardinality](/influxdb/cloud/reference/glossary/#series-cardinality)), this can quickly become many billions of points.
results would include ≈15.5 million points per series. Depending on the number of series returned after `filter()`([cardinality](/influxdb/v2.0/reference/glossary/#series-cardinality)), this can quickly become many billions of points.
Flux must store these points in memory to generate a response. Use [pushdown functions](#pushdown-functions) to optimize how many points are stored in memory.
To query data over large periods of time, create a task to [downsample data](/influxdb/v2.0/process-data/common-tasks/downsample-data/), and then query the downsampled data instead.