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
At the moment appmetrics-dash reports the CPU percentages used on the whole machine and by the Node.js process.
On a multi-core box this results in the Node.js process using very little of the total available CPU even if it is performing a CPU bound task. Node.js runs JavaScript code single threaded on the main libuv event loop thread. For example on an 8 way machine even if Node.js is running JavaScript in a tight loop it will only use a maximum of 12.5% of the total available CPU. We should report the percentage of one CPU that thread is using to give the user an idea of how much work is happening on the event loop thread so that in the above case the user could see that 100% of the CPU time available to run JavaScript code is in use.
We might not want to put this on the same chart as the CPU times for the process and system as those will be the percentage of multiple processors worth of CPU time.
(This is a similar problem to what we have seen with memory - the amount of memory used by Node.js is a fraction of what the system has even when it's performing badly.)
The text was updated successfully, but these errors were encountered:
At the moment appmetrics-dash reports the CPU percentages used on the whole machine and by the Node.js process.
On a multi-core box this results in the Node.js process using very little of the total available CPU even if it is performing a CPU bound task. Node.js runs JavaScript code single threaded on the main libuv event loop thread. For example on an 8 way machine even if Node.js is running JavaScript in a tight loop it will only use a maximum of 12.5% of the total available CPU. We should report the percentage of one CPU that thread is using to give the user an idea of how much work is happening on the event loop thread so that in the above case the user could see that 100% of the CPU time available to run JavaScript code is in use.
We might not want to put this on the same chart as the CPU times for the process and system as those will be the percentage of multiple processors worth of CPU time.
(This is a similar problem to what we have seen with memory - the amount of memory used by Node.js is a fraction of what the system has even when it's performing badly.)
The text was updated successfully, but these errors were encountered: