<?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[NETXMS Query taking too much resources]]></title><description><![CDATA[<p dir="auto">Hi All,</p>
<p dir="auto">The Query "INSERT INTO tdata_122 (item_id,tdata_timestamp,record_id) VALUES (:1,:2,:3)" is very expensive, it causes all sorts of problems with the Database including the creation of deadlocks and waits. Isn't there a way we can optimize it so as to make is less expensive on resources.</p>
]]></description><link>https://forum.netxms.org/topic/5741/netxms-query-taking-too-much-resources</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 08:25:14 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/5741.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 19 Nov 2018 14:01:42 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to NETXMS Query taking too much resources on Mon, 19 Nov 2018 18:42:11 GMT]]></title><description><![CDATA[<p dir="auto">Hi Alex</p>
<p dir="auto">Thanks for the Help, let me try to do what you have advised and monitor the difference.</p>
]]></description><link>https://forum.netxms.org/post/25042</link><guid isPermaLink="true">https://forum.netxms.org/post/25042</guid><dc:creator><![CDATA[isoftcom]]></dc:creator><pubDate>Mon, 19 Nov 2018 18:42:11 GMT</pubDate></item><item><title><![CDATA[Reply to NETXMS Query taking too much resources on Mon, 19 Nov 2018 18:21:48 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/isoftcom" aria-label="Profile: isoftcom">@<bdi>isoftcom</bdi></a> said in <a href="/post/25040">NETXMS Query taking too much resources</a>:</p>
<blockquote>
<p dir="auto">Is there way on how to tell netxms not to generate a lot of these history?</p>
</blockquote>
<p dir="auto">Sure.</p>
<ol>
<li>Increase collection interval for the table DCI (it's once a minute by default)</li>
<li>Decrease retention time for the table DCI (1 month by default)</li>
</ol>
<p dir="auto">You can change these settings per-DCI.</p>
<p dir="auto">To find out which DCI consume most of the space, you can query table in question:</p>
<pre><code>select item_id,count(*) c from tdata_122 group by item_id order by c desc;
</code></pre>
<p dir="auto">ID is the same as shown in data collection editor for the node</p>
]]></description><link>https://forum.netxms.org/post/25041</link><guid isPermaLink="true">https://forum.netxms.org/post/25041</guid><dc:creator><![CDATA[alk]]></dc:creator><pubDate>Mon, 19 Nov 2018 18:21:48 GMT</pubDate></item><item><title><![CDATA[Reply to NETXMS Query taking too much resources on Mon, 19 Nov 2018 18:12:37 GMT]]></title><description><![CDATA[<p dir="auto">I understand that the tdata_ table holds the DCI value history, my database is big with a lot of objects in the system sitting on oracle 11g database. The problem is the value history are alot and are taking a lot of resources when pushing these history to the database. Is there way on how to tell netxms not to generate a lot of these history?</p>
]]></description><link>https://forum.netxms.org/post/25040</link><guid isPermaLink="true">https://forum.netxms.org/post/25040</guid><dc:creator><![CDATA[isoftcom]]></dc:creator><pubDate>Mon, 19 Nov 2018 18:12:37 GMT</pubDate></item><item><title><![CDATA[Reply to NETXMS Query taking too much resources on Mon, 19 Nov 2018 14:39:11 GMT]]></title><description><![CDATA[<p dir="auto">It's simple insert with 3 field and single composite index, it should not be expensive.<br />
Please show explain / query plan.<br />
What DB you are using?<br />
How many objects in the system?<br />
How big the database is?<br />
What is retention time for tables DCIs on node 122?</p>
]]></description><link>https://forum.netxms.org/post/25038</link><guid isPermaLink="true">https://forum.netxms.org/post/25038</guid><dc:creator><![CDATA[alk]]></dc:creator><pubDate>Mon, 19 Nov 2018 14:39:11 GMT</pubDate></item></channel></rss>