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
{{ message }}
This repository was archived by the owner on Mar 9, 2022. It is now read-only.
Currently, during container stop, we poll every 0.1s to see whether a container is stopped.
When we stop a batch of containers, this may consume extra CPU.
We should add a channel stopCh for this in container metadata. Let event monitor close the channel, and stop function only need to wait for the channel.
Currently, during container stop, we poll every 0.1s to see whether a container is stopped.
When we stop a batch of containers, this may consume extra CPU.
We should add a channel
stopChfor this in container metadata. Let event monitor close the channel, and stop function only need to wait for the channel.@yanxuean @miaoyq