<?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: Inputlookup vs. summary index performance in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Inputlookup-vs-summary-index-performance/m-p/78720#M944</link>
    <description>&lt;P&gt;Depends on the size of the lookup table.   If it's less than 10MB, it's almost certainly faster to use inputlookup because it'll be sitting in memory already. &lt;/P&gt;

&lt;P&gt;&lt;A href="http://answers.splunk.com/questions/8326/are-lookup-tables-indexed" rel="nofollow"&gt;http://answers.splunk.com/questions/8326/are-lookup-tables-indexed&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;However bear in mind that you get all sorts of extra flexibility when you have summary indexing going.   It's not uncommon for a lookup solution to get replaced down the road by a summary index solution when you need that flexibility.  Like when the values start changing over time and you need to report on the changes.&lt;/P&gt;</description>
    <pubDate>Tue, 12 Apr 2011 12:34:25 GMT</pubDate>
    <dc:creator>sideview</dc:creator>
    <dc:date>2011-04-12T12:34:25Z</dc:date>
    <item>
      <title>Inputlookup vs. summary index performance</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Inputlookup-vs-summary-index-performance/m-p/78718#M942</link>
      <description>&lt;P&gt;If I have a bunch of events in a tabular format that I wish to search for various charts on a dashboard, is it faster to input the events with inputlookup or is it better to save them in a summary index and search the index?  &lt;/P&gt;

&lt;P&gt;Thx.  &lt;/P&gt;

&lt;P&gt;Craig&lt;/P&gt;</description>
      <pubDate>Mon, 11 Apr 2011 13:32:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Inputlookup-vs-summary-index-performance/m-p/78718#M942</guid>
      <dc:creator>jambajuice</dc:creator>
      <dc:date>2011-04-11T13:32:47Z</dc:date>
    </item>
    <item>
      <title>Re: Inputlookup vs. summary index performance</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Inputlookup-vs-summary-index-performance/m-p/78719#M943</link>
      <description>&lt;P&gt;I would think using a summary index would always be faster.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Apr 2011 01:48:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Inputlookup-vs-summary-index-performance/m-p/78719#M943</guid>
      <dc:creator>netwrkr</dc:creator>
      <dc:date>2011-04-12T01:48:53Z</dc:date>
    </item>
    <item>
      <title>Re: Inputlookup vs. summary index performance</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Inputlookup-vs-summary-index-performance/m-p/78720#M944</link>
      <description>&lt;P&gt;Depends on the size of the lookup table.   If it's less than 10MB, it's almost certainly faster to use inputlookup because it'll be sitting in memory already. &lt;/P&gt;

&lt;P&gt;&lt;A href="http://answers.splunk.com/questions/8326/are-lookup-tables-indexed" rel="nofollow"&gt;http://answers.splunk.com/questions/8326/are-lookup-tables-indexed&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;However bear in mind that you get all sorts of extra flexibility when you have summary indexing going.   It's not uncommon for a lookup solution to get replaced down the road by a summary index solution when you need that flexibility.  Like when the values start changing over time and you need to report on the changes.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Apr 2011 12:34:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Inputlookup-vs-summary-index-performance/m-p/78720#M944</guid>
      <dc:creator>sideview</dc:creator>
      <dc:date>2011-04-12T12:34:25Z</dc:date>
    </item>
  </channel>
</rss>

