<?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: heavy forwarder multi core? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/heavy-forwarder-multi-core/m-p/470911#M80939</link>
    <description>&lt;P&gt;If you increase the parallel ingestion pipelines on the forwarder (default = 1), it will utilize one core per pipeline.&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.1/Indexer/Pipelinesets#Forwarders_and_multiple_pipeline_sets"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.1/Indexer/Pipelinesets#Forwarders_and_multiple_pipeline_sets&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;One caveat worth noting, when handling compressed files (.gz) the forwarder will utilize a single pipeline only, regardless of the pipeline setting.&lt;/P&gt;</description>
    <pubDate>Wed, 12 Feb 2020 16:28:36 GMT</pubDate>
    <dc:creator>codebuilder</dc:creator>
    <dc:date>2020-02-12T16:28:36Z</dc:date>
    <item>
      <title>heavy forwarder multi core?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/heavy-forwarder-multi-core/m-p/470909#M80937</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I see a few similar questions in the past however I can't see an answer to date. &lt;/P&gt;

&lt;P&gt;Does anyone know if the splunkd process can utilise modern multicore cpu architectures? or is it bound to a single thread of execution?&lt;/P&gt;

&lt;P&gt;The splunk ingest pipeline looks to me (as a non-programmer) as something that might lend itself to multi-threading. &lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
David&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2020 10:48:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/heavy-forwarder-multi-core/m-p/470909#M80937</guid>
      <dc:creator>danan5</dc:creator>
      <dc:date>2020-02-12T10:48:39Z</dc:date>
    </item>
    <item>
      <title>Re: heavy forwarder multi core?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/heavy-forwarder-multi-core/m-p/470910#M80938</link>
      <description>&lt;P&gt;see here:&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/12027/single-multi-threading-cpu.html"&gt;https://answers.splunk.com/answers/12027/single-multi-threading-cpu.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;maybe this will help as well:&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.1/Capacity/Parallelization"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.1/Capacity/Parallelization&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2020 13:39:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/heavy-forwarder-multi-core/m-p/470910#M80938</guid>
      <dc:creator>adonio</dc:creator>
      <dc:date>2020-02-12T13:39:40Z</dc:date>
    </item>
    <item>
      <title>Re: heavy forwarder multi core?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/heavy-forwarder-multi-core/m-p/470911#M80939</link>
      <description>&lt;P&gt;If you increase the parallel ingestion pipelines on the forwarder (default = 1), it will utilize one core per pipeline.&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.1/Indexer/Pipelinesets#Forwarders_and_multiple_pipeline_sets"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.1/Indexer/Pipelinesets#Forwarders_and_multiple_pipeline_sets&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;One caveat worth noting, when handling compressed files (.gz) the forwarder will utilize a single pipeline only, regardless of the pipeline setting.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2020 16:28:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/heavy-forwarder-multi-core/m-p/470911#M80939</guid>
      <dc:creator>codebuilder</dc:creator>
      <dc:date>2020-02-12T16:28:36Z</dc:date>
    </item>
  </channel>
</rss>

