<?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: Performance of EXTRACT- vs REPORT- for same regex in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Performance-of-EXTRACT-vs-REPORT-for-same-regex/m-p/31181#M6422</link>
    <description>&lt;P&gt;Since they are both extracted by the same regex processor at search time, my educated guess would be no.&lt;/P&gt;

&lt;P&gt;Due to tradition, style, and readability, I personally tend to use the transforms.conf specification.&lt;/P&gt;</description>
    <pubDate>Tue, 25 Jan 2011 09:08:18 GMT</pubDate>
    <dc:creator>araitz</dc:creator>
    <dc:date>2011-01-25T09:08:18Z</dc:date>
    <item>
      <title>Performance of EXTRACT- vs REPORT- for same regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Performance-of-EXTRACT-vs-REPORT-for-same-regex/m-p/31180#M6421</link>
      <description>&lt;P&gt;Is there any difference in performance when using &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;props.conf
EXTRACT-name1 = long (?&amp;lt;field1&amp;gt;regex) with lots of (?&amp;lt;field2&amp;gt;capture groups)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;versus&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;props.conf
REPORT-name2 = transform_name

transforms.conf
[transform_name]
REGEX = long (regex) with lots of (capture groups)
FORMAT = field1::$1 field2::$2
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jan 2011 07:39:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Performance-of-EXTRACT-vs-REPORT-for-same-regex/m-p/31180#M6421</guid>
      <dc:creator>Jason</dc:creator>
      <dc:date>2011-01-25T07:39:10Z</dc:date>
    </item>
    <item>
      <title>Re: Performance of EXTRACT- vs REPORT- for same regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Performance-of-EXTRACT-vs-REPORT-for-same-regex/m-p/31181#M6422</link>
      <description>&lt;P&gt;Since they are both extracted by the same regex processor at search time, my educated guess would be no.&lt;/P&gt;

&lt;P&gt;Due to tradition, style, and readability, I personally tend to use the transforms.conf specification.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jan 2011 09:08:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Performance-of-EXTRACT-vs-REPORT-for-same-regex/m-p/31181#M6422</guid>
      <dc:creator>araitz</dc:creator>
      <dc:date>2011-01-25T09:08:18Z</dc:date>
    </item>
    <item>
      <title>Re: Performance of EXTRACT- vs REPORT- for same regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Performance-of-EXTRACT-vs-REPORT-for-same-regex/m-p/31182#M6423</link>
      <description>&lt;P&gt;Thanks - so do I. But I was working up a regex on the search bar with rex yesterday and tossed it right in an EXTRACT - so I was wondering.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jan 2011 00:30:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Performance-of-EXTRACT-vs-REPORT-for-same-regex/m-p/31182#M6423</guid>
      <dc:creator>Jason</dc:creator>
      <dc:date>2011-01-26T00:30:17Z</dc:date>
    </item>
    <item>
      <title>Re: Performance of EXTRACT- vs REPORT- for same regex</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Performance-of-EXTRACT-vs-REPORT-for-same-regex/m-p/31183#M6424</link>
      <description>&lt;P&gt;REPORT also allows you to apply the same regex easily to multiple data types without having multiple copies of the regex around - another reason why I use it.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jan 2011 02:01:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Performance-of-EXTRACT-vs-REPORT-for-same-regex/m-p/31183#M6424</guid>
      <dc:creator>Jason</dc:creator>
      <dc:date>2011-01-26T02:01:09Z</dc:date>
    </item>
  </channel>
</rss>

