Open JelteF opened 1 year ago
this is even the case for the background rebalancer citus_rebalance_start
yes that's correct. The planning itself is not done in the background, only the execution. Still I don't think it's a huge issue, since those 11 seconds were with ~8000 shard groups.
All of this time seems to be spent in getting the sizes of shard groups. It's doing one query per shard group to get the size of the complete shard group. We could optimize this by fetching sizes of all shards/shard groups from a node in one go. Probably by using
citus_shard_sizes()
.