<?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 the pony command in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/the-pony-command/m-p/74859#M15288</link>
    <description>&lt;P&gt;Hi Sirs,&lt;/P&gt;

&lt;P&gt;this is more a feature request than a question:&lt;/P&gt;

&lt;P&gt;why not include a performance test command for indexer (like bonnie++) and call it &lt;STRONG&gt;pony&lt;/STRONG&gt;?
this way the splunk user could run this test any time he wants from the search box and compare it with older test data to see if the performance on the indexer decreases or increases.&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
  &lt;P&gt;&lt;EM&gt;pony test now&lt;/EM&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;regards,
Michael&lt;/P&gt;</description>
    <pubDate>Tue, 05 Apr 2011 19:03:34 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2011-04-05T19:03:34Z</dc:date>
    <item>
      <title>the pony command</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/the-pony-command/m-p/74859#M15288</link>
      <description>&lt;P&gt;Hi Sirs,&lt;/P&gt;

&lt;P&gt;this is more a feature request than a question:&lt;/P&gt;

&lt;P&gt;why not include a performance test command for indexer (like bonnie++) and call it &lt;STRONG&gt;pony&lt;/STRONG&gt;?
this way the splunk user could run this test any time he wants from the search box and compare it with older test data to see if the performance on the indexer decreases or increases.&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
  &lt;P&gt;&lt;EM&gt;pony test now&lt;/EM&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;regards,
Michael&lt;/P&gt;</description>
      <pubDate>Tue, 05 Apr 2011 19:03:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/the-pony-command/m-p/74859#M15288</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2011-04-05T19:03:34Z</dc:date>
    </item>
    <item>
      <title>Re: the pony command</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/the-pony-command/m-p/74860#M15289</link>
      <description>&lt;P&gt;The pony is already alive, but called Deployment Monitor &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;In Splunk 4.2 you can &lt;STRONG&gt;enable&lt;/STRONG&gt; the &lt;STRONG&gt;Deployment Monitor App&lt;/STRONG&gt;. There you'll find exactly your needs (comparisons on indexers throughput prev. day/week vs. curr. day/week) and further useful stuff as well.&lt;/P&gt;

&lt;P&gt;UI --&amp;gt; Manager --&amp;gt; Apps --&amp;gt; Deployment Monitor&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2011 20:00:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/the-pony-command/m-p/74860#M15289</guid>
      <dc:creator>LCM</dc:creator>
      <dc:date>2011-04-06T20:00:33Z</dc:date>
    </item>
    <item>
      <title>Re: the pony command</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/the-pony-command/m-p/74861#M15290</link>
      <description>&lt;P&gt;We have found bonnie ++ to be particularly useful in troubleshooting issues where disk performance becomes a bottleneck. While deployment monitor provides metrics that are quite useful, as LCM indicates, it does not go as far as bonnie does with regard to providing statistics on disk IO. We see many cases where disk IO cannot sustain the required 800-100 IOPS, particularly when configured over NFS(not recommended). I will file this as a feature request for you with product management. &lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2011 22:47:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/the-pony-command/m-p/74861#M15290</guid>
      <dc:creator>jbsplunk</dc:creator>
      <dc:date>2011-04-06T22:47:08Z</dc:date>
    </item>
  </channel>
</rss>

