nicam
-
Posts
8 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by nicam
-
-
53 minutes ago, Derek said:
I agree, I am running plex and some other dockers. Raw CPU horsepower doesn't really concern me here, it just seems like this is an expensive command on any level of processing power if it's strictly for a display that is rarely viewed. Just surfing through some of the docker bug reports on the stats command, they seem to be well aware that it is an expensive command to run and do not have a fix in place yet. e.g.: https://github.com/docker/for-linux/issues/190
For example, my plex docker on unraid with hardware Intel Quick Sync transcoding of 1080p or 4k is able to easily serve my 2 endpoints at home without consuming much more than a constant 5-10% of CPU. Other containers don't consume much either -- as is the case similar to full blown VMs, having available RAM seems to be more important in most cases. I do run VMWare ESXi on a Xeon based server for most of my other needs that require more power, but I wanted to keep plex on my Unraid server because my Xeon does not have Intel Quick Sync.
I'll work on submitting a feature request.
Oh thank you very much, thanks to your comment I discovered that my CPU is QuickSync capable!
-
Is there any way to just turn it off? I don't really need the stats
-
Docker runs really well on this system I'm running Plex, Sonarr and about 10 other Containers with no issue.
-
I'm on 6.6.6 using an Intel J1900 Processor but seeing the exact same behaviour with the docker stats command constantly showing up with new PIDs
-
I have the exact same issue, have you figured out what's the culprit of it?
[6.6.1] docker stats command for cpu load and memory load running almost constantly
in Stable Releases
Posted
Thanks!