<?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: Datamodel Acceleration: How to make DM acceleration searches fast? in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Datamodel-Acceleration-How-to-make-DM-acceleration-searches-fast/m-p/316874#M2736</link>
    <description>&lt;P&gt;Upgrade to the latest release that has no &lt;CODE&gt;known issues&lt;/CODE&gt; for DMs.&lt;BR /&gt;
Add more RAM to your Indexers.&lt;BR /&gt;
Add more RAM to your Search Heads.&lt;BR /&gt;
Add more Indexers.&lt;BR /&gt;
Add more Search Heads.&lt;BR /&gt;
Make sure &lt;CODE&gt;pipelining&lt;/CODE&gt; is enabled (should be set to be equal to the number of CPU cores on that server).&lt;BR /&gt;
Run the Health Checks form &lt;CODE&gt;Monitoring Console&lt;/CODE&gt; and fix EVERYTHING (e.g. kill &lt;CODE&gt;THP&lt;/CODE&gt;).&lt;BR /&gt;
Make sure all of your searches are using &lt;CODE&gt;summariesonly=true&lt;/CODE&gt;.&lt;BR /&gt;
Hire a Consulting company to evaluate your environment and provide recommendations (there are many who do this, not just Splunk).&lt;/P&gt;</description>
    <pubDate>Mon, 04 Sep 2017 14:53:20 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2017-09-04T14:53:20Z</dc:date>
    <item>
      <title>Datamodel Acceleration: How to make DM acceleration searches fast?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Datamodel-Acceleration-How-to-make-DM-acceleration-searches-fast/m-p/316873#M2735</link>
      <description>&lt;P&gt;This query is for advanced tuning of Splunk Tiers so that the DM acceleration queries can run fast&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/ES/4.7.2/Install/Datamodels"&gt;http://docs.splunk.com/Documentation/ES/4.7.2/Install/Datamodels&lt;/A&gt; &lt;BR /&gt;
We have already done&lt;BR /&gt;
- Index specifics in DM , so it searches only specific Indexes&lt;BR /&gt;
- Load balancing on Indexers to get fast data as fast as possible&lt;BR /&gt;
- Reduced the retention as required and disabled unused DMs&lt;/P&gt;

&lt;P&gt;Other suggestions in our Mind&lt;BR /&gt;
1.  to mount /opt/splunk/var/run  in Search Head onto RAM (or SSD)&lt;BR /&gt;
2.  Customise the official TA's to remove unwanted fields for the customer. The effort vs return is NOT efficient here &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;BR /&gt;
3. Override unwanted eventtypes/tags as per customer requirements&lt;/P&gt;

&lt;P&gt;Any other suggestions from your side?&lt;/P&gt;</description>
      <pubDate>Mon, 04 Sep 2017 09:29:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Datamodel-Acceleration-How-to-make-DM-acceleration-searches-fast/m-p/316873#M2735</guid>
      <dc:creator>koshyk</dc:creator>
      <dc:date>2017-09-04T09:29:13Z</dc:date>
    </item>
    <item>
      <title>Re: Datamodel Acceleration: How to make DM acceleration searches fast?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Datamodel-Acceleration-How-to-make-DM-acceleration-searches-fast/m-p/316874#M2736</link>
      <description>&lt;P&gt;Upgrade to the latest release that has no &lt;CODE&gt;known issues&lt;/CODE&gt; for DMs.&lt;BR /&gt;
Add more RAM to your Indexers.&lt;BR /&gt;
Add more RAM to your Search Heads.&lt;BR /&gt;
Add more Indexers.&lt;BR /&gt;
Add more Search Heads.&lt;BR /&gt;
Make sure &lt;CODE&gt;pipelining&lt;/CODE&gt; is enabled (should be set to be equal to the number of CPU cores on that server).&lt;BR /&gt;
Run the Health Checks form &lt;CODE&gt;Monitoring Console&lt;/CODE&gt; and fix EVERYTHING (e.g. kill &lt;CODE&gt;THP&lt;/CODE&gt;).&lt;BR /&gt;
Make sure all of your searches are using &lt;CODE&gt;summariesonly=true&lt;/CODE&gt;.&lt;BR /&gt;
Hire a Consulting company to evaluate your environment and provide recommendations (there are many who do this, not just Splunk).&lt;/P&gt;</description>
      <pubDate>Mon, 04 Sep 2017 14:53:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Datamodel-Acceleration-How-to-make-DM-acceleration-searches-fast/m-p/316874#M2736</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-09-04T14:53:20Z</dc:date>
    </item>
    <item>
      <title>Re: Datamodel Acceleration: How to make DM acceleration searches fast?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Datamodel-Acceleration-How-to-make-DM-acceleration-searches-fast/m-p/316875#M2737</link>
      <description>&lt;P&gt;Thanks woodcock.&lt;/P&gt;

&lt;P&gt;Upgrade to the latest release that has no known issues for DMs.  =&amp;gt; Still to be done&lt;BR /&gt;
Add more RAM to your Indexers. =&amp;gt; Done. using 20% only&lt;BR /&gt;
Add more RAM to your Search Heads.  =&amp;gt; Done using 25% only&lt;BR /&gt;
Add more Indexers.  =&amp;gt; Have 48 of them&lt;BR /&gt;
Add more Search Heads.  =&amp;gt; Why this one? The client has 7, but how it can improve. The searches are still going on and parallel, but slow.&lt;BR /&gt;
Make sure pipelining is enabled (should be set to be equal to the number of CPU cores on that server).=&amp;gt; batch_search_max_pipeline is 2. Most of &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.6.3/Capacity/Parallelization" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/6.6.3/Capacity/Parallelization&lt;/A&gt; is done&lt;BR /&gt;
Run the Health Checks form Monitoring Console and fix EVERYTHING (e.g. kill THP). =&amp;gt; Nothing much showing errors other than slowness in search results&lt;BR /&gt;
Make sure all of your searches are using summariesonly=true.  =&amp;gt; The final searches are like that. But it is the "datamodel" acceleration searches which are the slow ones.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 15:36:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Datamodel-Acceleration-How-to-make-DM-acceleration-searches-fast/m-p/316875#M2737</guid>
      <dc:creator>koshyk</dc:creator>
      <dc:date>2020-09-29T15:36:37Z</dc:date>
    </item>
    <item>
      <title>Re: Datamodel Acceleration: How to make DM acceleration searches fast?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Datamodel-Acceleration-How-to-make-DM-acceleration-searches-fast/m-p/316876#M2738</link>
      <description>&lt;P&gt;I assumed this came up because searches are being skipped; if so, the surest way to fix that is more Search Heads.  For all I knew, you only had 1 (not mentioned in your OP).&lt;/P&gt;</description>
      <pubDate>Mon, 04 Sep 2017 16:31:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Datamodel-Acceleration-How-to-make-DM-acceleration-searches-fast/m-p/316876#M2738</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-09-04T16:31:27Z</dc:date>
    </item>
  </channel>
</rss>

