Skip to content

Commit bc2e905

Browse files
committed
Add kafka clickpipes benchmarks
1 parent b6274ee commit bc2e905

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

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

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -130,3 +130,16 @@ This requires scaling to at least two consumers.
130130
Regardless number of running consumers, fault tolerance is available by design.
131131
If a consumer or its underlying infrastructure fails,
132132
the ClickPipe will automatically restart the consumer and continue processing messages.
133+
134+
### Benchmarks {#benchmarks}
135+
136+
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.
137+
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.
139+
140+
| Replica Size | Message Size | Data Format | Throughput |
141+
|---------------|-----------|-------------|-----------|
142+
| 1vcpu/4gb | 1.6kb | JSON | 63mb/s |
143+
| 1vcpu/4gb | 1.6kb | AVRO | 99mb/s |
144+
145+

0 commit comments

Comments
 (0)