<?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: Why are infrastructure disk writes different than indexing rate in Splunk? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-infrastructure-disk-writes-different-than-indexing-rate/m-p/203351#M40167</link>
    <description>&lt;P&gt;The indexing rate only estimated indexing volume. Splunk searches, writing logs, optimizing/rolling buckets, and all other activities are not included. I'm not familiar with VM's measurement. So, I cannot tell what VMware's measurement procedure and time range etc.  Will VM guest iostat meet with the VMware's measurement? If so, probably that's what you need to compare. &lt;/P&gt;</description>
    <pubDate>Tue, 09 Aug 2016 19:05:54 GMT</pubDate>
    <dc:creator>Masa</dc:creator>
    <dc:date>2016-08-09T19:05:54Z</dc:date>
    <item>
      <title>Why are infrastructure disk writes different than indexing rate in Splunk?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-infrastructure-disk-writes-different-than-indexing-rate/m-p/203349#M40165</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;

&lt;P&gt;Basically, I am confused as to what is actually happening in our environment.  VMware shows that we are roughly writing at 6MB/s and Splunk Distributed Management Console shows indexing rate of 219KB/s.  So what is actually happening to magnify the writes so much?&lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/1670i1673690FED5AB30F/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/1671i7706D1F349F2ADEA/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 02 Aug 2016 20:33:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-infrastructure-disk-writes-different-than-indexing-rate/m-p/203349#M40165</guid>
      <dc:creator>edwardrose</dc:creator>
      <dc:date>2016-08-02T20:33:10Z</dc:date>
    </item>
    <item>
      <title>Re: Why are infrastructure disk writes different than indexing rate in Splunk?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-infrastructure-disk-writes-different-than-indexing-rate/m-p/203350#M40166</link>
      <description>&lt;P&gt;VM ware looks at the entire OS disk reads and writes. Slunk only considers it's own read write activity not of the entire disk /spinals read writes. Your disk are in array? I image they are and different parts of the disk spindles could be used in another vm.. but that's off topic... I think this could be the discrepancy. .. you could open resource monitor.. go to disk. Sort and calculate the splunk service disk activities and see if it roughly adds up to the index rate in the DMC on it indexer&lt;/P&gt;</description>
      <pubDate>Sat, 06 Aug 2016 00:54:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-infrastructure-disk-writes-different-than-indexing-rate/m-p/203350#M40166</guid>
      <dc:creator>Jarohnimo</dc:creator>
      <dc:date>2016-08-06T00:54:49Z</dc:date>
    </item>
    <item>
      <title>Re: Why are infrastructure disk writes different than indexing rate in Splunk?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Why-are-infrastructure-disk-writes-different-than-indexing-rate/m-p/203351#M40167</link>
      <description>&lt;P&gt;The indexing rate only estimated indexing volume. Splunk searches, writing logs, optimizing/rolling buckets, and all other activities are not included. I'm not familiar with VM's measurement. So, I cannot tell what VMware's measurement procedure and time range etc.  Will VM guest iostat meet with the VMware's measurement? If so, probably that's what you need to compare. &lt;/P&gt;</description>
      <pubDate>Tue, 09 Aug 2016 19:05:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Why-are-infrastructure-disk-writes-different-than-indexing-rate/m-p/203351#M40167</guid>
      <dc:creator>Masa</dc:creator>
      <dc:date>2016-08-09T19:05:54Z</dc:date>
    </item>
  </channel>
</rss>

