search

citusdata / citus_docs

Documentation for Citus. Distributed PostgreSQL as an extension.
Creative Commons Attribution 4.0 International
58 stars 59 forks source link

Docs On Cluster Sizing #331

Closed saicitus closed 6 years ago

saicitus commented 7 years ago

[## Why are we implementing it? (sales eng) Comes up in many sales-eng engagements.

What are the typical use cases?

Sharding on tenant - For OLTP mostly memory is important, for OLAP - Compute also comes into the picture. Coming up with a cluster size greater than or equal to the specs of their current db(say single node pg) setup is an option. Sharding helps in performance even if the cluster size equal to the specs of the current db because: 1) Queries are on smaller tables. 2) Less resource contention. 3) Adding tenant_id to tables/queries makes the queries optimized.

Sharding on entity - Mantra:Performance is directly proportional to the compute-number of cores (considering working set is in memory)

Communication goals (e.g. detailed howto vs orientation)

Good locations for content in docs structure

How does this work? (devs)

Example sql

Corner cases, gotchas

Are there relevant blog posts or outside documentation about the concept/feature?

Link to relevant commits and regression tests if applicable

](url)

sumedhpathak commented 7 years ago

@begriffs This looks like a dupe. Could you check if this content is now captured in our sizing section?

begriffs commented 6 years ago

Covered in https://docs.citusdata.com/en/v7.2/admin_guide/production_sizing.html