Hi, I'm using the helm charts to deploy signoz. Initially it deploys the clickhouse instance with a 20GB disk I only have a few apps with low traffic connected to the otel collector and after 20k traces in a day or two the disk of 20GB is already full. So it seems each trace occupy around 1MB of space in clickhouse. It seems to be huge ! Is it a normal behavior ?

can you show output of below command when run over clickhouse client

SELECT
                    database,
                    table,
                    formatReadableSize(sum(data_compressed_bytes) AS size) AS compressed,
                    formatReadableSize(sum(data_uncompressed_bytes) AS usize) AS uncompressed,
                    round(usize / size, 2) AS compr_rate,
                    sum(rows) AS rows,
                    count() AS part_count
                FROM system.parts
                WHERE (active = 1) AND (database='signoz_traces') AND (table LIKE '%')
                GROUP BY
                    database,
                    table
                ORDER BY size DESC;

Initially I ran select count() from signoz_metrics.time_series_v2; but seems I was on a different table

so 29M spans till now. Can you run the same query for logs and metrics dbs?

I only index traces SO the traces table is what I was looking for normally

ok..

So the issue seem to be on my side, I must figure out where thse 29M traces in a single day come from

maybe...though we will be optimizing the storage in a couple of weeks...a couple of features on duration and timestamp sorting in the trace filter page heavy on storage