Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Too many InfluxDB series #569

Closed
na-- opened this issue Apr 5, 2018 · 1 comment
Closed

Too many InfluxDB series #569

na-- opened this issue Apr 5, 2018 · 1 comment

Comments

@na--
Copy link
Member

na-- commented Apr 5, 2018

@danron reported in Slack:

It seems that the implementation of influxdb metrics is not following the recommended practice of not having too many series: https://docs.influxdata.com/influxdb/v1.5/concepts/schema_and_data_layout/#discouraged-schema-design. This since a new series is created for every vu and iteration, so the number of series will be metrics * vus * iterations. It would be better to change the tags vu and iter into fields for influxdb.

From the InfluxDB docs:

Tags containing highly variable information like UUIDs, hashes, and random strings will lead to a large number of series in the database, known colloquially as high series cardinality. High series cardinality is a primary driver of high memory usage for many database workloads.

Even though the iter and vu tags are not sent by default from v0.2.0, they could be manually enabled. We need an option that allows InfluxDB users to specify which of the tags they want to actually be sent as tags and which should be sent as fields. The default value should probably be vu,iter,url (name should probably remain as a tag, because it can be used for aggregation).

@na--
Copy link
Member Author

na-- commented Apr 20, 2018

This was closed by #585

@na-- na-- closed this as completed Apr 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant