<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Glances on Netdata</title><link>https://www.netdata.cloud/tags/glances/</link><description>Recent content in Glances on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 26 Sep 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/glances/index.xml" rel="self" type="application/rss+xml"/><item><title>Process Monitoring vs Console Tools: A Comparison</title><link>https://www.netdata.cloud/blog/netdata-processes-monitoring-comparison-with-console-tools/</link><pubDate>Tue, 26 Sep 2023 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/netdata-processes-monitoring-comparison-with-console-tools/</guid><description>&lt;p>Netdata reads &lt;code>/proc/&amp;lt;pid&amp;gt;/stat&lt;/code> for all processes, once per second and extracts &lt;code>utime&lt;/code> and
&lt;code>stime&lt;/code> (user and system cpu utilization), much like all the console tools do.&lt;/p>
&lt;p>But it also extracts &lt;code>cutime&lt;/code> and &lt;code>cstime&lt;/code> that account the user and system time of the exit children of each process.
By keeping a map in memory of the whole process tree, it is capable of assigning the right time to every process, taking
into account all its exited children.&lt;/p></description></item></channel></rss>