<?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: Reduce Splunk Forwarder RAM usage in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Reduce-Splunk-Forwarder-RAM-usage/m-p/77769#M15926</link>
    <description>&lt;P&gt;The author of the answer works for Splunk (head of engineering from memory) and knows the product inside out, back-to-front, and side-to-side... so his answer is about as definitive as it gets I'm afraid.&lt;/P&gt;</description>
    <pubDate>Tue, 20 Aug 2013 09:05:42 GMT</pubDate>
    <dc:creator>rturk</dc:creator>
    <dc:date>2013-08-20T09:05:42Z</dc:date>
    <item>
      <title>Reduce Splunk Forwarder RAM usage</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Reduce-Splunk-Forwarder-RAM-usage/m-p/77767#M15924</link>
      <description>&lt;P&gt;We are using a splunk universal forwarder on our virtual server systems and noticed that every instance uses about 70-80MB of RAM. This is more than 1800 MB of RAM on our 25 virtual systems. &lt;BR /&gt;
&lt;BR /&gt;Is there a way to reduce the memory usage of the Universal Forwarder by limiting a cache queue size or something?  &lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2013 12:56:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Reduce-Splunk-Forwarder-RAM-usage/m-p/77767#M15924</guid>
      <dc:creator>FRoth</dc:creator>
      <dc:date>2013-06-27T12:56:14Z</dc:date>
    </item>
    <item>
      <title>Re: Reduce Splunk Forwarder RAM usage</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Reduce-Splunk-Forwarder-RAM-usage/m-p/77768#M15925</link>
      <description>&lt;P&gt;I found this disappointing answer to my question. &lt;A href="http://answers.splunk.com/answers/47003/limit-the-memory-used-by-universal-forwarder"&gt;http://answers.splunk.com/answers/47003/limit-the-memory-used-by-universal-forwarder&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Aug 2013 08:44:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Reduce-Splunk-Forwarder-RAM-usage/m-p/77768#M15925</guid>
      <dc:creator>FRoth</dc:creator>
      <dc:date>2013-08-20T08:44:07Z</dc:date>
    </item>
    <item>
      <title>Re: Reduce Splunk Forwarder RAM usage</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Reduce-Splunk-Forwarder-RAM-usage/m-p/77769#M15926</link>
      <description>&lt;P&gt;The author of the answer works for Splunk (head of engineering from memory) and knows the product inside out, back-to-front, and side-to-side... so his answer is about as definitive as it gets I'm afraid.&lt;/P&gt;</description>
      <pubDate>Tue, 20 Aug 2013 09:05:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Reduce-Splunk-Forwarder-RAM-usage/m-p/77769#M15926</guid>
      <dc:creator>rturk</dc:creator>
      <dc:date>2013-08-20T09:05:42Z</dc:date>
    </item>
  </channel>
</rss>

