I recently deployed temporal connected to a new cassandra 3 node cluster in kubernetes. I set the numHistoryShards to 2048 in case we need them in future. I’ve noticed after deploying the services when there are no workers registered and no workflows to process that the history service is consistently sitting at around 20% - 30% cpu usage and that cassandra is also sitting around 20% - 30% cpu usage.
Is this the expected behaviour of temporal when there is nothing to process? Does the number of history shards affect the cpu usage?