Sizing and hardware recommendations

Consider using [ClickHouse Cloud](https://clickhouse.com/cloud) which scales automatically and allows you to easily control the number of replicas for your use case.

## Example configurations for large workloads[​](#example-configurations-for-large-workloads "Direct link to Example configurations for large workloads")

ClickHouse configurations are highly dependent on your specific application's requirements. Please [contact sales](https://clickhouse.com/company/contact?loc=docs-sizing-and-hardware-recommendations) if you would like us to help optimize your architecture for cost and performance.

To provide guidance (not recommendations), the following are example configurations of ClickHouse users in production:

### Fortune 500 B2B SaaS[​](#fortune-500-b2b-saas "Direct link to Fortune 500 B2B SaaS")

|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| ***Storage***| **Monthly new data volume** 30TB|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | **Total Storage (compressed)** 540TB|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | **Data retention** 18 months|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | **Disk per node** 25TB|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | ***CPU***| **Concurrency** 200+ concurrent queries|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | **# of replicas (including HA pair)** 44|  |  |  |  |  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | **vCPU per node** 62|  |  |  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | **Total vCPU** 2700|  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | ***Memory***| **Total RAM** 11TB|  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | | **RAM per replica** 256GB|  |  |  |  | | --- | --- | --- | --- | | **RAM-to-vCPU ratio** 4 GB:1|  |  | | --- | --- | | **RAM-to-disk ratio** 1:50 | | | | | | | | | | | | | | | | | | | | | | | | | | |

### Fortune 500 Telecom Operator for a logging use case[​](#fortune-500-telecom-operator-for-a-logging-use-case "Direct link to Fortune 500 Telecom Operator for a logging use case")

|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| ***Storage***| **Monthly log data volume** 4860TB|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | **Total Storage (compressed)** 608TB|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | **Data retention** 30 days|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | **Disk per node** 13TB|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | ***CPU***| **# of replicas (including HA pair)** 38|  |  |  |  |  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | **vCPU per node** 42|  |  |  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | **Total vCPU** 1600|  |  |  |  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | ***Memory***| **Total RAM** 10TB|  |  |  |  |  |  | | --- | --- | --- | --- | --- | --- | | **RAM per replica** 256GB|  |  |  |  | | --- | --- | --- | --- | | **RAM-to-vCPU ratio** 6 GB:1|  |  | | --- | --- | | **RAM-to-disk ratio** 1:60 | | | | | | | | | | | | | | | | | | | | | | | | |

## Further reading[​](#further-reading "Direct link to Further reading")

Below are published blog posts on architectures from companies using open-source ClickHouse:

- [Cloudflare](https://blog.cloudflare.com/http-analytics-for-6m-requests-per-second-using-clickhouse/?utm_source=linkedin&utm_medium=social&utm_campaign=blog)
- [eBay](https://innovation.ebayinc.com/tech/engineering/ou-online-analytical-processing/)
- [GitLab](https://handbook.gitlab.com/handbook/engineering/development/ops/monitor/observability/#clickhouse-datastore)
- [Lyft](https://eng.lyft.com/druid-deprecation-and-clickhouse-adoption-at-lyft-120af37651fd)
- [MessageBird](https://clickhouse.com/blog/how-messagebird-uses-clickhouse-to-monitor-the-delivery-of-billions-of-messages)
- [Microsoft](https://clickhouse.com/blog/self-service-data-analytics-for-microsofts-biggest-web-properties)
- [Uber](https://www.uber.com/en-ES/blog/logging/)
- [Zomato](https://blog.zomato.com/building-a-cost-effective-logging-platform-using-clickhouse-for-petabyte-scale)

- [Disk](#disk)
  - [Optimizing for performance](#optimizing-for-performance)- [Optimizing for storage costs](#optimizing-for-storage-costs)- [CPU](#cpu)
    - [Which CPU should I use?](#which-cpu-should-i-use)- [What should CPU utilization be?](#what-should-cpu-utilization-be)- [How many CPU cores should I use?](#how-many-cpu-cores-should-i-use)- [Memory](#memory)
      - [What should the memory-to-storage ratio be?](#what-should-the-memory-to-storage-ratio-be)- [Replicas](#replicas)- [Example configurations for large workloads](#example-configurations-for-large-workloads)
          - [Fortune 500 B2B SaaS](#fortune-500-b2b-saas)- [Fortune 500 Telecom Operator for a logging use case](#fortune-500-telecom-operator-for-a-logging-use-case)- [Further reading](#further-reading)

Was this page helpful?