kubeshark/tracer

Improve CPU, Memory consumption in Tracer

Closed this issue · 1 comments

At this point, Tracer consumes too much memory and CPU in a busy cluster.
We need to find a way to throttle the resource consumption.
One option is to use K8s resource throttling.

  • @iluxa to test and propose the right limits
  • @alongir to provide a few examples of high CPU and mem consumption by the Tracer [Please do not wait for this]
  • @alongir to review this PR

Example in a very little cluster:

Image

Significant improvement after this: kubeshark/kubeshark#1459
Should run more tests before we close this.