hi team! @nitya-signoz Today, we experienced slowness in the visualization of APM service metrics and constant restarts of the ClickHouse pod. The pod is configured with 5 CPUs and 7GB of memory. The pod logs show the following(image), Do I need to make any additional configurations to solve the problem? Note: The ClickHouse configuration is set to the default according to the SigNoz Chart version 0.43.0. logs otel-collector:

{"level":"info","timestamp":"2024-07-22T18:06:18.347Z","caller":"opamp/client.go:49","msg":"Ensuring collector is running","component":"opamp-server-client"}
2024-07-22T18:06:27.899Z	info	exporterhelper/retry_sender.go:177	Exporting failed. Will retry the request after interval.	{"kind": "exporter", "data_type": "metrics", "name": "clickhousemetricswrite", "error": "code: 252, message: Too many parts (3004 with average size of 60.39 KiB) in table 'signoz_metrics.samples_v2 (397bcd99-2abd-4864-a83c-3415499857de)'. Merges are processing significantly slower than inserts", "interval": "50ms"}
2024-07-22T18:06:28.084Z	info	exporterhelper/retry_sender.go:177	Exporting failed. Will retry the request after interval.	{"kind": "exporter", "data_type": "metrics", "name": "clickhousemetricswrite", "error": "code: 252, message: Too many parts (3004 with average size of 60.39 KiB) in table 'signoz_metrics.samples_v2 (397bcd99-2abd-4864-a83c-3415499857de)'. Merges are processing significantly slower than inserts", "interval": "0s"}

Can you share what is the batch size you are using? One of the ways is to increase the batch size and then increase the resources for clickhouse.