Currently for a service mesh with 100k+ mesh-wide requests (istio 1.1.x with policy disabled and mtls off) mixer uses up to 80 cores (only 2 adapters running: kubernetesenv and prometheus). This brings sizeable overhead to any cluster, thus increasing the operational costs.
I have tried to strip down metrics, rules and adapters (promtcpconnectionclosed, promtcpconnectionopen, tcpkubeattrgenrulerule, promtcp, promhttp) and the load only started to decrease when I deleted the kubeattrgenrulerule rule (the kubernetesenv adaptor had the most dispatches - 100k+).
Moreover, I have tried with different requests for the mixer pods, but same results.
Are there any plans to decrease this usage with the following Istio releases (1.2, 1.3)? I read that MixerV2 is coming, but I couldn’t find any docs or info about it - as far as I understood it will be at Envoy level. Will this change the cpu usage of istio-telemetry?