<?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 Summary Indexing vs. Data Model Acceleration - which is more performant? in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Summary-Indexing-vs-Data-Model-Acceleration-which-is-more/m-p/288371#M2540</link>
    <description>&lt;P&gt;I am trying to optimize searches that have large time spans (6+ months) with 10,000,000's of events. Which is more performant? Summary indexing or Data Model Acceleration? Conceptually I believe they would be similar in performance. &lt;/P&gt;</description>
    <pubDate>Thu, 04 Jan 2018 22:26:40 GMT</pubDate>
    <dc:creator>simpkins1958</dc:creator>
    <dc:date>2018-01-04T22:26:40Z</dc:date>
    <item>
      <title>Summary Indexing vs. Data Model Acceleration - which is more performant?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Summary-Indexing-vs-Data-Model-Acceleration-which-is-more/m-p/288371#M2540</link>
      <description>&lt;P&gt;I am trying to optimize searches that have large time spans (6+ months) with 10,000,000's of events. Which is more performant? Summary indexing or Data Model Acceleration? Conceptually I believe they would be similar in performance. &lt;/P&gt;</description>
      <pubDate>Thu, 04 Jan 2018 22:26:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Summary-Indexing-vs-Data-Model-Acceleration-which-is-more/m-p/288371#M2540</guid>
      <dc:creator>simpkins1958</dc:creator>
      <dc:date>2018-01-04T22:26:40Z</dc:date>
    </item>
    <item>
      <title>Re: Summary Indexing vs. Data Model Acceleration - which is more performant?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Summary-Indexing-vs-Data-Model-Acceleration-which-is-more/m-p/288372#M2541</link>
      <description>&lt;P&gt;I like a lot the &lt;CODE&gt;Summary Indexing&lt;/CODE&gt; feature and for any heavy duty app we set the &lt;CODE&gt;Summary Indexing&lt;/CODE&gt; as a foundation. The set up of the feature is completely transparent to you as an admin fellow, meaning, you control every aspect of it and you can validate it. Now I'm not sure how &lt;CODE&gt;Data Model Acceleration&lt;/CODE&gt; internally is being set up.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 00:43:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Summary-Indexing-vs-Data-Model-Acceleration-which-is-more/m-p/288372#M2541</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2018-01-05T00:43:22Z</dc:date>
    </item>
    <item>
      <title>Re: Summary Indexing vs. Data Model Acceleration - which is more performant?</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Summary-Indexing-vs-Data-Model-Acceleration-which-is-more/m-p/288373#M2542</link>
      <description>&lt;P&gt;Hi @simpkins1958,&lt;BR /&gt;
I think for your usecase summary index would be preferable because in splunk docs &lt;A href="http://docs.splunk.com/Documentation/Splunk/7.0.1/Knowledge/Acceleratedatamodels"&gt;http://docs.splunk.com/Documentation/Splunk/7.0.1/Knowledge/Acceleratedatamodels&lt;/A&gt;, it is mentioned that If you always plan to run a report over time ranges that exceed the past 7 days, but don't extend further out than 30 days, you should select a Summary Range of 1 month when you set up data model acceleration for that report. &lt;BR /&gt;
And in your case your searches have large time spans (6+ months).&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 07:32:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Summary-Indexing-vs-Data-Model-Acceleration-which-is-more/m-p/288373#M2542</guid>
      <dc:creator>nikita_p</dc:creator>
      <dc:date>2018-01-05T07:32:13Z</dc:date>
    </item>
  </channel>
</rss>

