<?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 Single/Multi Threading CPU in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Single-Multi-Threading-CPU/m-p/50439#M1609</link>
    <description>&lt;P&gt;Is splunk itself single or multi threading capable in a CPU architecture perspective?&lt;/P&gt;

&lt;P&gt;The docus I've read was mostly about x86 arch. but not SPARC!&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Example:&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;If splunk is multithreaded and I'm installing it on a T-series server (Sun) I might be faster than on a M-series server (Sun), cos T-series has more threads per core. On the other hand, if it's singlethreaded, I'm better on the M-series (less threads, but more power per thread), but that one is much more expensive.&lt;/P&gt;

&lt;P&gt;I know, who will install it these days on SPARC - sometimes politics wins!&lt;/P&gt;

&lt;P&gt;I read through some documentation, and I might have a guess: Single Threaded!&lt;/P&gt;</description>
    <pubDate>Fri, 25 Feb 2011 19:02:26 GMT</pubDate>
    <dc:creator>LCM</dc:creator>
    <dc:date>2011-02-25T19:02:26Z</dc:date>
    <item>
      <title>Single/Multi Threading CPU</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Single-Multi-Threading-CPU/m-p/50439#M1609</link>
      <description>&lt;P&gt;Is splunk itself single or multi threading capable in a CPU architecture perspective?&lt;/P&gt;

&lt;P&gt;The docus I've read was mostly about x86 arch. but not SPARC!&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Example:&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;If splunk is multithreaded and I'm installing it on a T-series server (Sun) I might be faster than on a M-series server (Sun), cos T-series has more threads per core. On the other hand, if it's singlethreaded, I'm better on the M-series (less threads, but more power per thread), but that one is much more expensive.&lt;/P&gt;

&lt;P&gt;I know, who will install it these days on SPARC - sometimes politics wins!&lt;/P&gt;

&lt;P&gt;I read through some documentation, and I might have a guess: Single Threaded!&lt;/P&gt;</description>
      <pubDate>Fri, 25 Feb 2011 19:02:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Single-Multi-Threading-CPU/m-p/50439#M1609</guid>
      <dc:creator>LCM</dc:creator>
      <dc:date>2011-02-25T19:02:26Z</dc:date>
    </item>
    <item>
      <title>Re: Single/Multi Threading CPU</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Single-Multi-Threading-CPU/m-p/50440#M1610</link>
      <description>&lt;P&gt;Take a look at this Splunk Answers:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://answers.splunk.com/questions/1829/splunk-searches-to-be-multithreaded-in-a-single-box" rel="nofollow"&gt;http://answers.splunk.com/questions/1829/splunk-searches-to-be-multithreaded-in-a-single-box&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;The short answer is that Splunk as a system is multi-threaded, but there are some Splunk processes that are not. Notably: indexing is multi-threaded, searches aren't. As gkanapathy mentions below, each search will use a single process and thread, so if you have 12 simultaneous searches, and a high indexing load, Splunk itself could use 16 threads.&lt;/P&gt;

&lt;P&gt;Perhaps an engineer can provide guidance if there is anything particular to SPARC systems, but I believe that link is representative.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Feb 2011 02:00:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Single-Multi-Threading-CPU/m-p/50440#M1610</guid>
      <dc:creator>David</dc:creator>
      <dc:date>2011-02-26T02:00:40Z</dc:date>
    </item>
    <item>
      <title>Re: Single/Multi Threading CPU</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Single-Multi-Threading-CPU/m-p/50441#M1611</link>
      <description>&lt;P&gt;In the thread you posted, silvermails answer explains it best (for me). While searching, one core is beeing clamed and the rest ist idling (single-thread) - Thanks David for the hint!&lt;/P&gt;</description>
      <pubDate>Sat, 26 Feb 2011 23:25:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Single-Multi-Threading-CPU/m-p/50441#M1611</guid>
      <dc:creator>LCM</dc:creator>
      <dc:date>2011-02-26T23:25:31Z</dc:date>
    </item>
    <item>
      <title>Re: Single/Multi Threading CPU</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Single-Multi-Threading-CPU/m-p/50442#M1612</link>
      <description>&lt;P&gt;That is incorrect. The indexing process is multi-threaded, up to four or more threads, though in practice you'll usually see two.&lt;/P&gt;</description>
      <pubDate>Sun, 27 Feb 2011 06:56:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Single-Multi-Threading-CPU/m-p/50442#M1612</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-02-27T06:56:23Z</dc:date>
    </item>
    <item>
      <title>Re: Single/Multi Threading CPU</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Single-Multi-Threading-CPU/m-p/50443#M1613</link>
      <description>&lt;P&gt;Furthermore, each concurrent search uses a full process and thread.&lt;/P&gt;</description>
      <pubDate>Sun, 27 Feb 2011 06:56:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Single-Multi-Threading-CPU/m-p/50443#M1613</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-02-27T06:56:48Z</dc:date>
    </item>
    <item>
      <title>Re: Single/Multi Threading CPU</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Single-Multi-Threading-CPU/m-p/50444#M1614</link>
      <description>&lt;P&gt;All that said, please do not analogize Splunk with a web server for the purposes of sizing and multithreading. It is much more analogous to a database server, in that CPU and threads are only a small part of the performance factors, and rarely the most important ones.&lt;/P&gt;</description>
      <pubDate>Sun, 27 Feb 2011 06:58:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Single-Multi-Threading-CPU/m-p/50444#M1614</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-02-27T06:58:22Z</dc:date>
    </item>
    <item>
      <title>Re: Single/Multi Threading CPU</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Single-Multi-Threading-CPU/m-p/50445#M1615</link>
      <description>&lt;P&gt;Thanks for the corrections. I fixed the errors in my original answer, should anyone read it in the future and skip over comments.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Mar 2011 02:25:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Single-Multi-Threading-CPU/m-p/50445#M1615</guid>
      <dc:creator>David</dc:creator>
      <dc:date>2011-03-01T02:25:45Z</dc:date>
    </item>
  </channel>
</rss>

