<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Splunk universal forwarder performance in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-universal-forwarder-performance/m-p/44429#M8307</link>
    <description>&lt;P&gt;I was looking in the $SPLUNK_HOME/etc/system/default/limits.conf file and didn't look in that directory.&lt;/P&gt;

&lt;P&gt;I've made the change to 1024 and see the increased indexer activity.&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Sat, 25 Aug 2012 20:03:53 GMT</pubDate>
    <dc:creator>wsweat</dc:creator>
    <dc:date>2012-08-25T20:03:53Z</dc:date>
    <item>
      <title>Splunk universal forwarder performance</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-universal-forwarder-performance/m-p/44427#M8305</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;Is there a performance guide for the universal forwarder (v 4.3.3)?&lt;/P&gt;

&lt;P&gt;The indexer is running at 2 events per second and I'm only running one universal forwarder. The indexer has 16 cores and 16GB of mem and I'm having the forwarder send over a dozen, or so, files that range from a 100MB - 20GB. Both systems are underutilized for both memory and cpu (server load is around 0.5 on both).&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sat, 25 Aug 2012 18:18:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-universal-forwarder-performance/m-p/44427#M8305</guid>
      <dc:creator>wsweat</dc:creator>
      <dc:date>2012-08-25T18:18:13Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk universal forwarder performance</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-universal-forwarder-performance/m-p/44428#M8306</link>
      <description>&lt;P&gt;There is no guide, but in terms of thruput note the following: &lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;A Universal Forwarder is capable of outputting at a much higher rate than a typical indexer can properly ingest. &lt;/LI&gt;
&lt;LI&gt;A Universal Forwarder's default thruput is capped at 256KBps:&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;&lt;CODE&gt;$SPLUNK_HOME/etc/apps/SplunkUniversalForwarder/default/limits.conf&lt;BR /&gt;
[thruput]&lt;BR /&gt;
maxKBps = 256&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Hope this helps.&lt;/P&gt;

&lt;P&gt;d.&lt;/P&gt;</description>
      <pubDate>Sat, 25 Aug 2012 19:01:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-universal-forwarder-performance/m-p/44428#M8306</guid>
      <dc:creator>_d_</dc:creator>
      <dc:date>2012-08-25T19:01:44Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk universal forwarder performance</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-universal-forwarder-performance/m-p/44429#M8307</link>
      <description>&lt;P&gt;I was looking in the $SPLUNK_HOME/etc/system/default/limits.conf file and didn't look in that directory.&lt;/P&gt;

&lt;P&gt;I've made the change to 1024 and see the increased indexer activity.&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Sat, 25 Aug 2012 20:03:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-universal-forwarder-performance/m-p/44429#M8307</guid>
      <dc:creator>wsweat</dc:creator>
      <dc:date>2012-08-25T20:03:53Z</dc:date>
    </item>
  </channel>
</rss>

