Open ongsunglau opened 2 months ago
NCPA uses the PSUtil library to get system diagnostic information. If PSUtil gives incorrect information for whatever reason, then NCPA will also have incorrect information. Another possibility cause is that NCPA gets diagnostic information over a fairly short period of time at the moment, meaning spikes and valleys in usage can cause differing values, though I think that is not likely to be the case here.
As for a workaround, you could create a plugin that uses prstat/top to get your memory information and then access the plugins/myplugin.sh
endpoint instead of memory/virtual/percent
Hi Dev Team,
We noticed that 2.3.1 ncpa get different results of memory usage from actual server consumed by process.
What we can able to workaround or method to fix this?
In prstat/top process results
https://127.0.0.1:5693/gui/api results
This is active check we are using