Understand why resource usage of master components is noticeably different in Kubemark

We see pretty big discrepancy between what we see in kubemark clusters and real ones. It needs to be understood. Difference is mostly in the API server usage.

E.g. 99 percentile in kubemark (both results from after Density, which is run as a first test):

container                               cpu(cores) memory(MB)
"apiserver/apiserver"                   0.606      407.89
"controller-manager/controller-manager" 0.120      218.27
"etcd/etcd/data"                        0.120      160.75
"etcd/etcd/data-events"                 0.034      46.22
"scheduler/scheduler"                   0.080      114.16

and real cluster:

    {
      "Name": "etcd-server-e2e-scalability-master/etcd-container",
      "Cpu": 0.167254853,
      "Mem": 371601408
    },
    {
      "Name": "etcd-server-events-e2e-scalability-master/etcd-container",
      "Cpu": 0.14851711,
      "Mem": 159068160
    },
    {
      "Name": "kube-apiserver-e2e-scalability-master/kube-apiserver",
      "Cpu": 0.972463425,
      "Mem": 787206144
    },
    {
      "Name": "kube-controller-manager-e2e-scalability-master/kube-controller-manager",
      "Cpu": 0.180771427,
      "Mem": 235991040
    },
    {
      "Name": "kube-scheduler-e2e-scalability-master/kube-scheduler",
      "Cpu": 0.169906087,
      "Mem": 113385472
    },

@wojtek-t @shyamjvs @kubernetes/sig-scalability-misc