You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environment:
perfspect version 3.6.1_2025-04-28_4282e576
Ubuntu 22.04
kernel 6.8.0-1024-aws
EC2_INSTANCE_TYPE=m7i.metal-24xl
Issue: Perfspect does not resume collection when old containers stop and new containers spawned, but rather remains in hang state.
How to reproduce:
Run a container with some benchmark (say stress-ng), invoke perfspect with this command line "sudo ./perfspect metrics --live --scope cgroup", it correctly collects metrics per c-group every default (5s) interval. However, if the container is stopped, perfspect stops sending any stdout, which is also correct. Now when a new container is spwaned, it does not pick it up even after the 30s refresh interval.
Likely my environment, or the refresh is not catching the new container/cgroup correctly and resuming collection?
The text was updated successfully, but these errors were encountered:
Environment:
perfspect version 3.6.1_2025-04-28_4282e576
Ubuntu 22.04
kernel 6.8.0-1024-aws
EC2_INSTANCE_TYPE=m7i.metal-24xl
Issue: Perfspect does not resume collection when old containers stop and new containers spawned, but rather remains in hang state.
How to reproduce:
Run a container with some benchmark (say stress-ng), invoke perfspect with this command line "sudo ./perfspect metrics --live --scope cgroup", it correctly collects metrics per c-group every default (5s) interval. However, if the container is stopped, perfspect stops sending any stdout, which is also correct. Now when a new container is spwaned, it does not pick it up even after the 30s refresh interval.
Likely my environment, or the refresh is not catching the new container/cgroup correctly and resuming collection?
The text was updated successfully, but these errors were encountered: