<?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 reduce high memory usage? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Datamodel-Acceleration-How-to-reduce-high-memory-usage/m-p/453136#M78512</link>
    <description>&lt;P&gt;I don't have ES. Here is specs&lt;BR /&gt;
1 SH  (RHEL):&lt;BR /&gt;
8 CPU, 12 Gb of RAM, Splunk 7.0.2&lt;BR /&gt;
3 Indexers (RHEL)&lt;BR /&gt;
16 CPU, 24 Gb of RAM, Splunk 7.0.2&lt;/P&gt;

&lt;P&gt;This DMA didn't complete as indexers systems are killing splunk processes for high memory usage.&lt;BR /&gt;
But other DMAs (on other DM) work perfectly.&lt;/P&gt;

&lt;P&gt;All accelerated DMs are restricted to specific index.&lt;BR /&gt;
I'm pretty afraid about increasing the number of concurrent acceleration as enabling this one (proxy DMA) is already causing high memory usage. Currently it is set to 1.&lt;/P&gt;

&lt;P&gt;I didn't know about skew settings. I'll take a look.&lt;BR /&gt;
Thanks for the hand. I'll let you know if it helps &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 02 Jul 2019 09:38:00 GMT</pubDate>
    <dc:creator>olivier_ma</dc:creator>
    <dc:date>2019-07-02T09:38:00Z</dc:date>
    <item>
      <title>Datamodel Acceleration: How to reduce high memory usage?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Datamodel-Acceleration-How-to-reduce-high-memory-usage/m-p/453134#M78510</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I'm facing a high memory usage on all of the 3 indexers when I try to accelerate a datamodel, even for 1 day acceleration.&lt;BR /&gt;
After investigation, high memory usage is due to searches run for datamodel acceleration.&lt;BR /&gt;
Our indexers have 20Gb of RAM. The accelerated datamodel is about proxy logs (~60Gb / day) and it's an root-event based datamodel.&lt;/P&gt;

&lt;P&gt;How can I debug this issue ?&lt;BR /&gt;
Did I miss something on datamodel acceleration ?&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2019 14:04:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Datamodel-Acceleration-How-to-reduce-high-memory-usage/m-p/453134#M78510</guid>
      <dc:creator>olivier_ma</dc:creator>
      <dc:date>2019-07-01T14:04:36Z</dc:date>
    </item>
    <item>
      <title>Re: Datamodel Acceleration: How to reduce high memory usage?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Datamodel-Acceleration-How-to-reduce-high-memory-usage/m-p/453135#M78511</link>
      <description>&lt;P&gt;What are your specs of the ES SH and the indexers? Are your DMAs completing in time?&lt;BR /&gt;
Did you restrict the DM to the specific index(es)? You can also try increasing the number of instances assigned to the DMA, this can also be done via UI (or &lt;CODE&gt;acceleration.max_concurrent&lt;/CODE&gt; in datamodels.conf).&lt;BR /&gt;
Did you set skewing (called &lt;CODE&gt;allow_skew&lt;/CODE&gt; ) for scheduled searches &lt;STRONG&gt;and&lt;/STRONG&gt; DMA already?&lt;/P&gt;

&lt;P&gt;If you still run into issues after doing some tuning, you might wanna contact support/PS about further improvements.&lt;/P&gt;

&lt;P&gt;Skalli&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2019 17:19:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Datamodel-Acceleration-How-to-reduce-high-memory-usage/m-p/453135#M78511</guid>
      <dc:creator>skalliger</dc:creator>
      <dc:date>2019-07-01T17:19:41Z</dc:date>
    </item>
    <item>
      <title>Re: Datamodel Acceleration: How to reduce high memory usage?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Datamodel-Acceleration-How-to-reduce-high-memory-usage/m-p/453136#M78512</link>
      <description>&lt;P&gt;I don't have ES. Here is specs&lt;BR /&gt;
1 SH  (RHEL):&lt;BR /&gt;
8 CPU, 12 Gb of RAM, Splunk 7.0.2&lt;BR /&gt;
3 Indexers (RHEL)&lt;BR /&gt;
16 CPU, 24 Gb of RAM, Splunk 7.0.2&lt;/P&gt;

&lt;P&gt;This DMA didn't complete as indexers systems are killing splunk processes for high memory usage.&lt;BR /&gt;
But other DMAs (on other DM) work perfectly.&lt;/P&gt;

&lt;P&gt;All accelerated DMs are restricted to specific index.&lt;BR /&gt;
I'm pretty afraid about increasing the number of concurrent acceleration as enabling this one (proxy DMA) is already causing high memory usage. Currently it is set to 1.&lt;/P&gt;

&lt;P&gt;I didn't know about skew settings. I'll take a look.&lt;BR /&gt;
Thanks for the hand. I'll let you know if it helps &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2019 09:38:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Datamodel-Acceleration-How-to-reduce-high-memory-usage/m-p/453136#M78512</guid>
      <dc:creator>olivier_ma</dc:creator>
      <dc:date>2019-07-02T09:38:00Z</dc:date>
    </item>
    <item>
      <title>Re: Datamodel Acceleration: How to reduce high memory usage?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Datamodel-Acceleration-How-to-reduce-high-memory-usage/m-p/453137#M78513</link>
      <description>&lt;P&gt;How much are you ingesting per day and what is the size of the mentioned DM?&lt;BR /&gt;
If only the big DMA doesn't get completed in time right now, skewing could help but in the long term you might wanna add another indexer to distribute the load further.&lt;/P&gt;

&lt;P&gt;Skalli&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2019 09:49:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Datamodel-Acceleration-How-to-reduce-high-memory-usage/m-p/453137#M78513</guid>
      <dc:creator>skalliger</dc:creator>
      <dc:date>2019-07-02T09:49:39Z</dc:date>
    </item>
    <item>
      <title>Re: Datamodel Acceleration: How to reduce high memory usage?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Datamodel-Acceleration-How-to-reduce-high-memory-usage/m-p/453138#M78514</link>
      <description>&lt;P&gt;Configure BOTH &lt;CODE&gt;index=&lt;/CODE&gt; AND &lt;CODE&gt;sourcetype=&lt;/CODE&gt; in your &lt;CODE&gt;cim_&amp;lt;DMA&amp;gt;_index&lt;/CODE&gt; macros.&lt;BR /&gt;
Configure tags whitelist.&lt;BR /&gt;
Check out the &lt;CODE&gt;known issues&lt;/CODE&gt; page of the release notes for your release and implement the workarounds listed for the DMA bugs for your version (there are some DOOZIES).&lt;BR /&gt;
Get more RAM for your Search Heads and Indexers and RESERVE IT EXCLUSIVELY if in a VM.&lt;BR /&gt;
Deploy more Indexers.&lt;/P&gt;</description>
      <pubDate>Sat, 06 Jul 2019 03:05:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Datamodel-Acceleration-How-to-reduce-high-memory-usage/m-p/453138#M78514</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-07-06T03:05:19Z</dc:date>
    </item>
  </channel>
</rss>

