<?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: Splunk cloud - AWS - COncurrent searches in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Splunk-cloud-AWS-COncurrent-searches/m-p/427608#M122426</link>
    <description>&lt;P&gt;Search capability, including concurrency has nothing to do with indexed volume.  It is mostly constrained by CPU cores on the search head, plus settings, intersecting with actual demand.  Read more here:&lt;BR /&gt;
&lt;A href="https://www.rfaircloth.com/2017/12/12/tuning-splunk-when-max-concurrent-searches-are-reached/"&gt;https://www.rfaircloth.com/2017/12/12/tuning-splunk-when-max-concurrent-searches-are-reached/&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 27 Apr 2019 01:05:24 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2019-04-27T01:05:24Z</dc:date>
    <item>
      <title>Splunk cloud - AWS - COncurrent searches</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-cloud-AWS-COncurrent-searches/m-p/427607#M122425</link>
      <description>&lt;P&gt;say, I have a splunk cloud,, Splunk as a service running in AWS with a daily index volume of 10 GB data per day. what is the maximum number of concurrent searches allowed? if there is any performance in concurrent searching, how to scale up?  &lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2019 12:57:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-cloud-AWS-COncurrent-searches/m-p/427607#M122425</guid>
      <dc:creator>dhivyam</dc:creator>
      <dc:date>2019-04-26T12:57:51Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk cloud - AWS - COncurrent searches</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-cloud-AWS-COncurrent-searches/m-p/427608#M122426</link>
      <description>&lt;P&gt;Search capability, including concurrency has nothing to do with indexed volume.  It is mostly constrained by CPU cores on the search head, plus settings, intersecting with actual demand.  Read more here:&lt;BR /&gt;
&lt;A href="https://www.rfaircloth.com/2017/12/12/tuning-splunk-when-max-concurrent-searches-are-reached/"&gt;https://www.rfaircloth.com/2017/12/12/tuning-splunk-when-max-concurrent-searches-are-reached/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 27 Apr 2019 01:05:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-cloud-AWS-COncurrent-searches/m-p/427608#M122426</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-04-27T01:05:24Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk cloud - AWS - COncurrent searches</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-cloud-AWS-COncurrent-searches/m-p/427609#M122427</link>
      <description>&lt;P&gt;Thanks much for you response. &lt;BR /&gt;
I understood from the docs that concurrent searches are related to CPU cores but If it's a Splunk enterprise version we have control over infrastructure.  when it's Splunk cloud where do not know about the CPU cores/infra, how many concurrent searches are allowed with better performance?&lt;/P&gt;</description>
      <pubDate>Mon, 29 Apr 2019 11:23:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-cloud-AWS-COncurrent-searches/m-p/427609#M122427</guid>
      <dc:creator>dhivyam</dc:creator>
      <dc:date>2019-04-29T11:23:15Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk cloud - AWS - COncurrent searches</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-cloud-AWS-COncurrent-searches/m-p/427610#M122428</link>
      <description>&lt;P&gt;Math is not the right approach here.  Instead monitor for logs that clearly indicate either &lt;CODE&gt;queued&lt;/CODE&gt; or &lt;CODE&gt;skipped&lt;/CODE&gt; searches.  If you have these, you have some kind of concurrency problem.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Apr 2019 04:49:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-cloud-AWS-COncurrent-searches/m-p/427610#M122428</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-04-30T04:49:08Z</dc:date>
    </item>
  </channel>
</rss>

