local-path-provisioner icon indicating copy to clipboard operation
local-path-provisioner copied to clipboard

High CPU Usage

Open mschae opened this issue 5 years ago • 1 comments

See #14

I am using k3s on a i5 and the local path provisioner (version v0.0.11) sits at 18% CPU: grafik

Steps to reproduce:

  1. Install k3s on x86 Hardware
  2. Use the local path provisioner

Interestingly enough I am also running k3s on a cloud server, not using the local-path-provisioner (but having it running) and it doesn't consume nearly as many resources there.

mschae avatar Feb 05 '20 10:02 mschae

I'm seeing this as well, with v0.0.11. For me, cpu usage starts low if I delete the pod and let it recreate, then after a while I see it back up in my top consumers.

I've just updated the manifest to v0.0.12 and will see if the issue persists.

mshade avatar May 03 '20 03:05 mshade