<?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 Memory Usage by streamfwd.exe in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Memory-Usage-by-streamfwd-exe/m-p/523155#M88359</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have recently deployed Splunk TA Stream on universal forwarder to collect DNS data. Stream App is configured on heavy Forwarder. The universal forwarder is forwarding the data to indexer cluster.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The streamfwd.exe service on DNS server is consuming 1GB of memory. Is it a normal behavior of streamfwd.exe service to use memory in GB?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;UF host details : Windows 2012 R2 , Memory : 32 GB , 64bit&lt;/P&gt;&lt;P&gt;Below configurations on Universal Forwarder:&lt;/P&gt;&lt;P&gt;limits.conf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;maxKbps = 4096&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;inputs.conf&lt;/P&gt;&lt;PRE&gt;[streamfwd://streamfwd]
splunk_stream_app_location = https://&amp;lt;HF_IP&amp;gt;:8000/en-us/custom/splunk_app_stream/
disabled = 0&lt;BR /&gt;&lt;SPAN&gt;stream_forwarder_id = &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;sslVerifyServerCert = false&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 06 Oct 2020 11:02:20 GMT</pubDate>
    <dc:creator>ashajambagi</dc:creator>
    <dc:date>2020-10-06T11:02:20Z</dc:date>
    <item>
      <title>Memory Usage by streamfwd.exe</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Memory-Usage-by-streamfwd-exe/m-p/523155#M88359</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have recently deployed Splunk TA Stream on universal forwarder to collect DNS data. Stream App is configured on heavy Forwarder. The universal forwarder is forwarding the data to indexer cluster.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The streamfwd.exe service on DNS server is consuming 1GB of memory. Is it a normal behavior of streamfwd.exe service to use memory in GB?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;UF host details : Windows 2012 R2 , Memory : 32 GB , 64bit&lt;/P&gt;&lt;P&gt;Below configurations on Universal Forwarder:&lt;/P&gt;&lt;P&gt;limits.conf&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;maxKbps = 4096&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;inputs.conf&lt;/P&gt;&lt;PRE&gt;[streamfwd://streamfwd]
splunk_stream_app_location = https://&amp;lt;HF_IP&amp;gt;:8000/en-us/custom/splunk_app_stream/
disabled = 0&lt;BR /&gt;&lt;SPAN&gt;stream_forwarder_id = &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;sslVerifyServerCert = false&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2020 11:02:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Memory-Usage-by-streamfwd-exe/m-p/523155#M88359</guid>
      <dc:creator>ashajambagi</dc:creator>
      <dc:date>2020-10-06T11:02:20Z</dc:date>
    </item>
    <item>
      <title>Re: Memory Usage by streamfwd.exe</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Memory-Usage-by-streamfwd-exe/m-p/523209#M88371</link>
      <description>&lt;P&gt;How busy is your DNS server?&lt;/P&gt;&lt;P&gt;Also, you've limited the maxKbps of the UF to 4 Mb.&amp;nbsp; If during busy times the DNS entries exceed 4 Mb, then it just buffers it all, and that would use a lot of memory.&lt;/P&gt;&lt;P&gt;If I were you, I'd raise those limits WAY up higher, or remove then completely, and see what change that makes.&amp;nbsp; Try it at 'maxKbps=0'&amp;nbsp; (Which is unlimited)&lt;/P&gt;&lt;P&gt;You can always set it back to something less than unlimited after testing proves this solves it or does not solve it.&amp;nbsp; Frankly, I'd just leave it set to unlimited and build out indexer ingestion if you have to.&amp;nbsp; The only reasons I can think of to leave it limited is to not fill a small pipe, like a WAN connection that's underprovisioned for what's needed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Happy Splunking,&lt;/P&gt;&lt;P&gt;Rich&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2020 14:23:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Memory-Usage-by-streamfwd-exe/m-p/523209#M88371</guid>
      <dc:creator>Richfez</dc:creator>
      <dc:date>2020-10-06T14:23:42Z</dc:date>
    </item>
  </channel>
</rss>

