-
Notifications
You must be signed in to change notification settings - Fork 52
Clarify space partitioning due to multi-node #564
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 8000 . We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
api.md
Outdated
**Space partitions**: Using space partitions is highly recommended | ||
for [distributed hypertables](#create_distributed_hypertable) to achieve | ||
efficient scale-out performance. For [regular hypertables](#create_hypertable) | ||
that exist only a single node, the use of additional partitioning is a |
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.
only on a?
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.
I improved this place.
across multiple disks within the same time interval | ||
(in the case of single-node deployments). | ||
|
||
### Parallelizing queries across multiple data nodes [](add_dimension-multi_node) |
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.
Curious if we should move this sections somewhere else, like performance or optimization
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.
I suggest to discuss and consider this outside this PR.
Space partitioning is rare case for non-distributed hypertables, but is important for multi-node to be effective. This commit clarifies this.
Space partitioning is rare case for non-distributed hypertables, but is
important for multi-node to be effective. This commit clarifies this.