<?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: earliest_time in POST call versus earliest in query itself in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/earliest-time-in-POST-call-versus-earliest-in-query-itself/m-p/367902#M5996</link>
    <description>&lt;P&gt;Aside from the fact that you're snapping to the day in one search and not the other, there should be no difference in performance.&lt;/P&gt;</description>
    <pubDate>Sat, 12 Aug 2017 19:55:22 GMT</pubDate>
    <dc:creator>jkat54</dc:creator>
    <dc:date>2017-08-12T19:55:22Z</dc:date>
    <item>
      <title>earliest_time in POST call versus earliest in query itself</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/earliest-time-in-POST-call-versus-earliest-in-query-itself/m-p/367901#M5995</link>
      <description>&lt;P&gt;I am sending a POST call to the REST endpoint &lt;CODE&gt;search/jobs&lt;/CODE&gt; with following parameters:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;    'output_mode': 'json',
    'earliest_time': '-7d',
    'latest_time': '-1d',
    'exec_mode': 'oneshot',
    'search': 'search index=ind status=FAIL | table error, sim_time'
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;If, instead of above, I send:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;    'output_mode': 'json',
    'exec_mode': 'oneshot',
    'search': 'search index=ind earliest=-7d@d latest=-1d@d status=FAIL | table error, sim_time'
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Is there a difference? In terms of performance, load on server, correctness etc.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Aug 2017 18:53:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/earliest-time-in-POST-call-versus-earliest-in-query-itself/m-p/367901#M5995</guid>
      <dc:creator>shikhanshu</dc:creator>
      <dc:date>2017-08-12T18:53:10Z</dc:date>
    </item>
    <item>
      <title>Re: earliest_time in POST call versus earliest in query itself</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/earliest-time-in-POST-call-versus-earliest-in-query-itself/m-p/367902#M5996</link>
      <description>&lt;P&gt;Aside from the fact that you're snapping to the day in one search and not the other, there should be no difference in performance.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Aug 2017 19:55:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/earliest-time-in-POST-call-versus-earliest-in-query-itself/m-p/367902#M5996</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2017-08-12T19:55:22Z</dc:date>
    </item>
    <item>
      <title>Re: earliest_time in POST call versus earliest in query itself</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/earliest-time-in-POST-call-versus-earliest-in-query-itself/m-p/367903#M5997</link>
      <description>&lt;P&gt;Sorry, I missed the @d in one search! Both searches are supposed to be the same. No difference sounds great!&lt;/P&gt;</description>
      <pubDate>Sat, 12 Aug 2017 19:58:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/earliest-time-in-POST-call-versus-earliest-in-query-itself/m-p/367903#M5997</guid>
      <dc:creator>shikhanshu</dc:creator>
      <dc:date>2017-08-12T19:58:01Z</dc:date>
    </item>
    <item>
      <title>Re: earliest_time in POST call versus earliest in query itself</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/earliest-time-in-POST-call-versus-earliest-in-query-itself/m-p/367904#M5998</link>
      <description>&lt;P&gt;You can always test both 10-20 times and avaerage the results.  The _internal index has data related to how long the searches took.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Aug 2017 20:01:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/earliest-time-in-POST-call-versus-earliest-in-query-itself/m-p/367904#M5998</guid>
      <dc:creator>jkat54</dc:creator>
      <dc:date>2017-08-12T20:01:31Z</dc:date>
    </item>
  </channel>
</rss>

