March-9th-2018, 06:36 AM
Hello Michael,
please find appended a screen shot I made using the top command on the linux host. You see that the cifx0daemon costs just 2%-3% of CPU resources from a global view.
I googled to find any information on the web whether or not the top command works 100% the same in a container as outside, but I wasn't able to find such kind of information.
What I can tell you is that the daemon periodically calls for incoming network message cause there is no event driven communication realized between both CPUs. So you will see CPU usage even if there is no traffic on the network present and is idle.
With this result I would say it is accepted and the daemon is working normal.
please find appended a screen shot I made using the top command on the linux host. You see that the cifx0daemon costs just 2%-3% of CPU resources from a global view.
I googled to find any information on the web whether or not the top command works 100% the same in a container as outside, but I wasn't able to find such kind of information.
What I can tell you is that the daemon periodically calls for incoming network message cause there is no event driven communication realized between both CPUs. So you will see CPU usage even if there is no traffic on the network present and is idle.
With this result I would say it is accepted and the daemon is working normal.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
