You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure that it could be considered as an issue, but any help will be appreciated.
We decided to upgrade the ClickHouse client version from v1.5.3 to v2.2.0.
We were hoping that it can improve writing (insertion speed).
We cannot use the latest CH client version (2.6) because of some kind of library incompatibility.
Got this during the building
github.com/Unity-Technologies/mz-user-value/vendor/github.com/segmentio/asm/bswap.swap64: relocation target github.com/segmentio/asm/cpu.X86 not defined
The command '/bin/sh -c go install -v ./...' returned a non-zero code: 2
After upgrading we got the performance degradation, the batch commit latency increased twice:
See the code example how we measured latency.
Also, we got a higher memory usage:
Some details about the use case.
The service is running in GCP on 6 pods of n1-standard-64 machines type.
The service costume data from Kafka and insert into CH.
The CH cluster runs on 4 nodes (2 shards and 2 replicas) of n2-standard-16 machines.
The insertion rate 400k-500k records/sec (could be 600k at peak).
We use batch insertion, the batch size 2M records.
Thanks for reporting this. This is, unfortunately, a known issue, and we got it already reported at #856
We will most likely have to invest more time in the upcoming weeks to improve performance. I am a third-in-a-row maintainer for this project. I don't think the performance was a real concern during developing v2.
Issue description
Not sure that it could be considered as an issue, but any help will be appreciated.
We decided to upgrade the ClickHouse client version from v1.5.3 to v2.2.0.
We were hoping that it can improve writing (insertion speed).
We cannot use the latest CH client version (2.6) because of some kind of library incompatibility.
Got this during the building
After upgrading we got the performance degradation, the batch commit latency increased twice:
See the code example how we measured latency.
Also, we got a higher memory usage:
Some details about the use case.
The service is running in GCP on 6 pods of n1-standard-64 machines type.
The service costume data from Kafka and insert into CH.
The CH cluster runs on 4 nodes (2 shards and 2 replicas) of n2-standard-16 machines.
The insertion rate 400k-500k records/sec (could be 600k at peak).
We use batch insertion, the batch size 2M records.
Example code
Client initialization:
Insert SQL statement:
The tables:
Prepare batch
Insert:
Commit (send) measurement code
Where the
batch
is defined as:Error log
N/A
Configuration
OS:
Interface: E.g.
native
Driver version: 2.2.0
Go version: run
go version
in your consoleClickHouse Server version: 22.3.8.39
The text was updated successfully, but these errors were encountered: