Skip to content

Commit 90af6bb

Browse files
committed
more details
1 parent bc2e905 commit 90af6bb

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

docs/integrations/data-ingestion/clickpipes/kafka/04_best_practices.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,14 @@ the ClickPipe will automatically restart the consumer and continue processing me
135135

136136
Below are some informal benchmarks for ClickPipes for Kafka that can be used get a general idea of ClickPipes performance. It is important to know that many factors can impact performance including message size, data types, and data format. Your mileage may vary, and what we show here is not a guarantee of performance.
137137

138-
We used production ClickHouse Cloud services with enough resources to ensure that throughput was not bottlenecked by the insert processing on the ClickHouse side.
138+
Benchmark details:
139+
- We used production ClickHouse Cloud services with enough resources to ensure that throughput was not bottlenecked by the insert processing on the ClickHouse side.
140+
- The ClickHouse Cloud service, the Kafka cluster (confluent), and the ClickPipe were all running in the same region (us-east-2).
141+
- The ClickPipe was configured with a single consumer.
142+
- The sample data included nested data with a mix of uuid, string, and integer datatypes.
143+
- Other datatypes, such as floats may be less performant.
144+
- There was no appreciable differene in performance between compressed and uncompressed data.
145+
139146

140147
| Replica Size | Message Size | Data Format | Throughput |
141148
|---------------|-----------|-------------|-----------|

0 commit comments

Comments
 (0)