<?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: Disk space requirements in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Disk-space-requirements/m-p/187917#M37513</link>
    <description>&lt;P&gt;The general rule of thumb I've been taught is to take your raw data size and figure about 50% of that on disk including indexes. This is due to compression reducing the size significantly, and indexing adding to the size on disk. &lt;/P&gt;

&lt;P&gt;Of course, this is a rule of thumb, YMMV. It is recommended that you simply test it by indexing some data (e.g. with a day's or week's worth of data) and see how large the files are on disk. The actual compression / index size can vary significantly. &lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2014 13:31:05 GMT</pubDate>
    <dc:creator>adauria_splunk</dc:creator>
    <dc:date>2014-06-04T13:31:05Z</dc:date>
    <item>
      <title>Disk space requirements</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Disk-space-requirements/m-p/187916#M37512</link>
      <description>&lt;P&gt;I need to get a vague idea of disk space requirements before I start forwarding logs to a Splunk instance. Each indexed line will have on average 320 characters and I will be indexing around 500,000 lines a day.&lt;/P&gt;

&lt;P&gt;My assumptions are 1 byte per character and I'm ignoring space taken by Splunk for indices, etc. That's 160MB per day.&lt;/P&gt;

&lt;P&gt;Would you say that's semi-accurate or totally off the mark?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2014 12:58:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Disk-space-requirements/m-p/187916#M37512</guid>
      <dc:creator>mcamilleri</dc:creator>
      <dc:date>2014-06-04T12:58:32Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space requirements</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Disk-space-requirements/m-p/187917#M37513</link>
      <description>&lt;P&gt;The general rule of thumb I've been taught is to take your raw data size and figure about 50% of that on disk including indexes. This is due to compression reducing the size significantly, and indexing adding to the size on disk. &lt;/P&gt;

&lt;P&gt;Of course, this is a rule of thumb, YMMV. It is recommended that you simply test it by indexing some data (e.g. with a day's or week's worth of data) and see how large the files are on disk. The actual compression / index size can vary significantly. &lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2014 13:31:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Disk-space-requirements/m-p/187917#M37513</guid>
      <dc:creator>adauria_splunk</dc:creator>
      <dc:date>2014-06-04T13:31:05Z</dc:date>
    </item>
    <item>
      <title>Re: Disk space requirements</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Disk-space-requirements/m-p/187918#M37514</link>
      <description>&lt;P&gt;Thanks! I don't have ready access to a Splunk instance - but that ballpark estimate should do for now.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2014 13:34:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Disk-space-requirements/m-p/187918#M37514</guid>
      <dc:creator>mcamilleri</dc:creator>
      <dc:date>2014-06-04T13:34:15Z</dc:date>
    </item>
  </channel>
</rss>

