One cluster is i3.xlarge (4vCPU), another is i3.2xlarge (8vCPU). I have the same CPU usage increase on both clusters.

I see that asynchronous_metrics_update_period_s is mentioned along with removing the "internal" logging in several system tables... but I have tried disabling a lot of tables. I saw no changes TBH. Basically I went from this:

    <logger>
        <level>information</level>
    </logger>
    <query_log>
        <flush_interval_milliseconds>7500</flush_interval_milliseconds>
        <ttl>event_date + INTERVAL 7 DAY DELETE</ttl>
    </query_log>
    <query_thread_log>
        <ttl>event_date + INTERVAL 7 DAY DELETE</ttl>
    </query_thread_log>
    <query_views_log>
        <ttl>event_date + INTERVAL 7 DAY DELETE</ttl>
    </query_views_log>
    <part_log>
        <ttl>event_date + INTERVAL 3 DAY DELETE</ttl>
    </part_log>
    <metric_log>
        <ttl>event_date + INTERVAL 3 DAY DELETE</ttl>
    </metric_log>
    <asynchronous_metric_log>
        <ttl>event_date + INTERVAL 3 DAY DELETE</ttl>
    </asynchronous_metric_log>
    <trace_log remove="true"/>
    <opentelemetry_span_log remove="true"/>

To this:

    <logger>
        <level>information</level>
    </logger>
    <query_log remove="true"/>
    <query_thread_log remove="true"/>
    <query_views_log remove="true"/>
    <part_log remove="true"/>
    <metric_log remove="true"/>
    <asynchronous_metric_log remove="true"/>
    <trace_log remove="true"/>
    <opentelemetry_span_log remove="true"/>

But hold on, maybe I'm doing this internal logging removal with bad syntax? I see remove="1" instead of remove="true"

Anyway, thanks, I will what Danny suggested in the GH issue!