<?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 Impact of real-time distributed searches on CPU utilization? in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Impact-of-real-time-distributed-searches-on-CPU-utilization/m-p/75309#M892</link>
    <description>&lt;P&gt;What is the impact of running real-time searches across a Splunk cluster, both for the dedicated search head and the associated search peers? &lt;/P&gt;

&lt;P&gt;The rule of thumb is that one search is one CPU core, does that also apply to distributed search (per peer)? So if your search peers have 8 cores, 8 real-time queries will consume all the cores, effectively grinding the cluster to a halt. Is my understanding correct?&lt;/P&gt;

&lt;P&gt;Is there a functional difference between Splunk versions (I am particularly interested in 5.0.3)?&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Tue, 25 Jun 2013 20:57:49 GMT</pubDate>
    <dc:creator>gregbujak</dc:creator>
    <dc:date>2013-06-25T20:57:49Z</dc:date>
    <item>
      <title>Impact of real-time distributed searches on CPU utilization?</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Impact-of-real-time-distributed-searches-on-CPU-utilization/m-p/75309#M892</link>
      <description>&lt;P&gt;What is the impact of running real-time searches across a Splunk cluster, both for the dedicated search head and the associated search peers? &lt;/P&gt;

&lt;P&gt;The rule of thumb is that one search is one CPU core, does that also apply to distributed search (per peer)? So if your search peers have 8 cores, 8 real-time queries will consume all the cores, effectively grinding the cluster to a halt. Is my understanding correct?&lt;/P&gt;

&lt;P&gt;Is there a functional difference between Splunk versions (I am particularly interested in 5.0.3)?&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2013 20:57:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Impact-of-real-time-distributed-searches-on-CPU-utilization/m-p/75309#M892</guid>
      <dc:creator>gregbujak</dc:creator>
      <dc:date>2013-06-25T20:57:49Z</dc:date>
    </item>
    <item>
      <title>Re: Impact of real-time distributed searches on CPU utilization?</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Impact-of-real-time-distributed-searches-on-CPU-utilization/m-p/75310#M893</link>
      <description>&lt;P&gt;As far as my understanding goes (will have to owe you the documentation) a real-time search won't consume an entire core. What I mean by this is that multiple real-time searches will share cores and therefore increase how many concurrent real-time searches you can run.&lt;/P&gt;

&lt;P&gt;Look in the limits.conf for the real time search limits and the concurrent limits. I think they give an explanation of how it works there.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2013 21:03:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Impact-of-real-time-distributed-searches-on-CPU-utilization/m-p/75310#M893</guid>
      <dc:creator>aholzer</dc:creator>
      <dc:date>2013-06-25T21:03:52Z</dc:date>
    </item>
    <item>
      <title>Re: Impact of real-time distributed searches on CPU utilization?</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Impact-of-real-time-distributed-searches-on-CPU-utilization/m-p/75311#M894</link>
      <description>&lt;P&gt;HI Alek, thanks for the response. Limits.conf does specify the max number real-time searches, but it doesn't explain how it works. So what would happen if we allow 8 rt queries at the same time?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jun 2013 21:43:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Impact-of-real-time-distributed-searches-on-CPU-utilization/m-p/75311#M894</guid>
      <dc:creator>gregbujak</dc:creator>
      <dc:date>2013-06-25T21:43:41Z</dc:date>
    </item>
    <item>
      <title>Re: Impact of real-time distributed searches on CPU utilization?</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Impact-of-real-time-distributed-searches-on-CPU-utilization/m-p/75312#M895</link>
      <description>&lt;P&gt;I realized that joins in the RT query caused the acceleration to mis-behave. In the face of fast moving data, each instance of the same RT query would eat its share of the CPU (on my machine it was 20% per request). However, while expensive, in 6.0 this has been fixed. So now complex RT queries (with joins) are accelerated and work as expected. &lt;/P&gt;

&lt;P&gt;The reality is that with fast moving data, instances of different RT queries will quickly consume all the cpu resources and grind the system to a halt. &lt;/P&gt;</description>
      <pubDate>Fri, 25 Oct 2013 20:56:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Impact-of-real-time-distributed-searches-on-CPU-utilization/m-p/75312#M895</guid>
      <dc:creator>gregbujak</dc:creator>
      <dc:date>2013-10-25T20:56:07Z</dc:date>
    </item>
    <item>
      <title>Re: Impact of real-time distributed searches on CPU utilization?</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Impact-of-real-time-distributed-searches-on-CPU-utilization/m-p/75313#M896</link>
      <description>&lt;P&gt;Remember that searches run on the Indexers, the compiling of data and post processing of the data happens on the search heads.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Oct 2013 23:09:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Impact-of-real-time-distributed-searches-on-CPU-utilization/m-p/75313#M896</guid>
      <dc:creator>ShaneNewman</dc:creator>
      <dc:date>2013-10-25T23:09:18Z</dc:date>
    </item>
  </channel>
</rss>

