Closed gorghino closed 2 months ago
Ask clickhouse community?
We do not do anything special from our side. Just push and read records.
Hi @bsekachev tnks for the answer. Are those numbers similar to your machine as well? Also I'm not very familiar with it and I don't know if this is may be related to some cvat env setting.
I do not see any problems with number of threads. It does not affect overall performance.
For anyone with the same doubt: it's intentional.
You can retrieve the threads by type (logging inside the container and installing procps apk --no-cache add procps
) with:
ps H -o 'tid comm' $(pidof -s clickhouse-server) | tail -n +2 | awk '{ printf("%s\t%s\n", $1, $2) }' | clickhouse-local -S "threadid UInt16, name String" -q "SELECT name, count() FROM table GROUP BY name WITH TOTALS ORDER BY count() DESC FORMAT PrettyCompact"
By default background_schedule_pool_size is 512. The others are in different groups. The clickhouse community also claimed the threads can go up to 3-5k under workload.
Actions before raising this issue
Steps to Reproduce
Expected Behavior
A reasonable number of used threads (?)
Possible Solution
No response
Context
I'm not sure if this's intentional or not, but I recently found that my clickhouse-server process is using 708 threads. The CPU/Mem usage seems ok though.
Environment