<?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[Syslog Performance]]></title><description><![CDATA[<p dir="auto">Does anyone else on here use the syslog feature with InnoDB? We keep having catastrophic performance issues when using it in any production capacity. How do others deal with this?</p>
]]></description><link>https://forum.netxms.org/topic/5738/syslog-performance</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 09:43:02 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/5738.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 15 Nov 2018 05:10:55 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Syslog Performance on Thu, 15 Nov 2018 09:08:21 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">what NetXMS version you are using? How many syslog records you are receiving? I know there are quite big installations on PostgreSQL that are writing lot of syslog messages. You can try to increase server configuration parameter DBWriter.MaxRecordsPerTransaction - that can increase transaction size and speed up inserts.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/25027</link><guid isPermaLink="true">https://forum.netxms.org/post/25027</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Thu, 15 Nov 2018 09:08:21 GMT</pubDate></item></channel></rss>