-
Notifications
You must be signed in to change notification settings - Fork 51
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
De-emphasize wide data models #27
Conversation
introduction/data-model.md
Outdated
same timestamp, since it requires writing a timestamp for each metric. This ultimately | ||
results in higher storage and ingest requirements. Further, if you typically query multiple | ||
metrics together, it is faster to store them in a wide table format, which we will cover | ||
in the following section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also queries are more complex if you want to correlate different values. Every further value you want to correlate requires another JOIN
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed
introduction/data-model.md
Outdated
|
||
Our wide-table model actually looks exactly the same as the initial data stream: | ||
TimescaleDB easily supports wide-table models. A typical wide-table model would match | ||
a typical data stream in which multiple metrics are collected at a given timestamp: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Queries involving multiple values are much easier with this model, as they require no joins.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed
Approved, but please address @svenklemm 's comments. |
f5125a3
to
cca6a61
Compare
Addressed comments. Merging! |
This de-emphasizes the discussion on wide data models, and provides rationales for when a narrow data model might make sense. This reflects the advice we give to users, as well as the observed schemas we see users deploy.