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

Will shorter tag name and field name help reduce the database size? #3554

Closed
airyland opened this issue Aug 5, 2015 · 3 comments
Closed

Comments

@airyland
Copy link

airyland commented Aug 5, 2015

I wonder if it's necessary to use shorter name for tags or fileds name?

@beckettsean
Copy link
Contributor

Tag keys and values are only stored once, so their length is effectively irrelevant to total storage size.

I believe field keys are also only stored once and referenced by ID rather than the raw string, so field key length should also be irrelevant to total on disk size. I'm asking for confirmation on that.

There are compression fixes coming in 0.9.3 (#3544) that will also reduce the on disk representation.

@airyland
Copy link
Author

airyland commented Aug 6, 2015

Cool. Thx.

@beckettsean
Copy link
Contributor

@airyland I verified that only a field key ID is stored with the point, so there's no meaningful difference in your on-disk data size for large tag keys, tag values, or field keys. Only the size of field values has any impact on the total disk used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants