Running the election MacOS app, close the octant UI and observe the resource utilization for octant. The background process is consuming between 120-160% of a cpu core. This is pure backend load even when there is no client connected.
What did you expect to happen:
I'd expect the backend to use some CPU cycles just to keep the caches alive for when the front end connects. Maybe 5-10% of a CPU core is acceptable.
Environment:
Octant version (use octant version): 0.17.0
Kubernetes version (use kubectl version): 1.17
OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): macOS 11.2.1 (Rossetta)
What steps did you take and what happened:
Running the election MacOS app, close the octant UI and observe the resource utilization for octant. The background process is consuming between 120-160% of a cpu core. This is pure backend load even when there is no client connected.
What did you expect to happen:
I'd expect the backend to use some CPU cycles just to keep the caches alive for when the front end connects. Maybe 5-10% of a CPU core is acceptable.
Environment:
octant version
): 0.17.0kubectl version
): 1.17