<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[about the "disk queue" between netxms and "iostat"]]></title><description><![CDATA[<p dir="auto">Hi:<br />
I used the netxms1.1.6, Linux<br />
I found the System.IO.DiskQueue to get the disk queue value in netxms is far different from that I get with "iostat" tool. (Event the netxms flush the value in one minutes and iostat flush the value in one second)<br />
So I saw the source code in netxms and iostat. Both of then get the value through the /proc/diskstats. they get the value is such like that:</p>
<p dir="auto">   8    0 sda 34567 17159 1358372 355080 20268 49302 556588 1263830 1 150950 1622600<br />
                                                                                                  |                |<br />
                                                                                              netxms          iostate</p>
<p dir="auto">but the netxms get the 11th value ( it is 1 ) while the iostate get the last one (it is 1622600) to do the calculation.</p>
<p dir="auto">I want to know,if the concept of "disk queue"  in netxms is different from that in "iostat"?    or what's the  definition of "disk queue" in netxms.</p>
<p dir="auto">Thanks!</p>
]]></description><link>https://forum.netxms.org/topic/1640/about-the-disk-queue-between-netxms-and-iostat</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 06:47:07 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/1640.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 23 Mar 2012 02:00:42 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to about the "disk queue" between netxms and "iostat" on Tue, 27 Mar 2012 07:38:24 GMT]]></title><description><![CDATA[<p dir="auto">That's very interesting, because at least on my system iostat's result are consistent with value given by NetXMS agent. Can you point me to exact place in iostat source code?</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/7099</link><guid isPermaLink="true">https://forum.netxms.org/post/7099</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Tue, 27 Mar 2012 07:38:24 GMT</pubDate></item><item><title><![CDATA[Reply to about the "disk queue" between netxms and "iostat" on Tue, 27 Mar 2012 02:42:12 GMT]]></title><description><![CDATA[<p dir="auto">Thanks for your answer.<br />
But I saw the  iostat source code,and found that, the  iostat  get the disk queue with the  Field 11 — weighted # of milliseconds spent doing I/Os<br />
while netxms with the Field 9 — # of I/Os currently in progress.</p>
<p dir="auto">So I think, may be there is something wrong with the iostat to get the disk queue value.</p>
]]></description><link>https://forum.netxms.org/post/7094</link><guid isPermaLink="true">https://forum.netxms.org/post/7094</guid><dc:creator><![CDATA[x199x]]></dc:creator><pubDate>Tue, 27 Mar 2012 02:42:12 GMT</pubDate></item><item><title><![CDATA[Reply to about the "disk queue" between netxms and "iostat" on Sat, 24 Mar 2012 16:12:06 GMT]]></title><description><![CDATA[<p dir="auto">Hi!</p>
<p dir="auto">/proc/diskstats has the following fields (numbering started after device name):</p>
<p dir="auto">Field 1 — # of reads issued<br />
Field 2 — # of reads merged<br />
Field 3 — # of sectors read<br />
Field 4 — # of milliseconds spent reading<br />
Field 5 — # of writes completed<br />
Field 6 — # of writes merged<br />
Field 7 — # of sectors written<br />
Field 8 — # of milliseconds spent writing<br />
Field 9 — # of I/Os currently in progress<br />
Field 10 — # of milliseconds spent doing I/Os<br />
Field 11 — weighted # of milliseconds spent doing I/Os</p>
<p dir="auto">NetXMS agent gets field #9 (# of I/Os currently in progress) to calculate average disk queue size. And "disk queue" means "number of disk I/O requests that are either in service or waiting for service". In iostat, it's a parameter called avgqu-sz (shown if running with -x command line option). On my NetXMS server it looks like this:</p>
<pre><code>root@netxms:~# iostat -x 1
Linux 2.6.32-5-686 (netxms)     03/24/2012      _i686_  (2 CPU)

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           8.26    0.00    2.39    3.24    0.00   86.11

Device:         rrqm/s   wrqm/s     r/s     w/s   rsec/s   wsec/s avgrq-sz avgqu-sz   await  svctm  %util
cciss/c0d0        0.02    39.01    3.07   26.43   265.29   523.52    26.74     0.17    5.64   3.27   9.66

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           0.50    0.00    1.50    2.00    0.00   96.00

Device:         rrqm/s   wrqm/s     r/s     w/s   rsec/s   wsec/s avgrq-sz avgqu-sz   await  svctm  %util
cciss/c0d0        0.00    13.00    0.00   13.00     0.00   208.00    16.00     0.05    4.00   4.00   5.20

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           3.45    0.00    1.48    0.49    0.00   94.58

Device:         rrqm/s   wrqm/s     r/s     w/s   rsec/s   wsec/s avgrq-sz avgqu-sz   await  svctm  %util
cciss/c0d0        0.00     8.00    0.00    3.00     0.00    88.00    29.33     0.02    6.67   4.00   1.20

^C
root@netxms:~# nxget 127.0.0.1 "System.IO.DiskQueue(cciss/c0d0)"
0.033333
root@netxms:~#
</code></pre>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/7088</link><guid isPermaLink="true">https://forum.netxms.org/post/7088</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Sat, 24 Mar 2012 16:12:06 GMT</pubDate></item></channel></rss>