<?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: Indexer Sizing in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-Sizing/m-p/757729#M120182</link>
    <description>&lt;P&gt;This is the kind of question you go to your local friendly Splunk Partner with, not some randoms on the internet.&lt;/P&gt;&lt;P&gt;There are many factors possibly affecting your environment size and overall architecture - search load, retention, HA requirements...&lt;/P&gt;&lt;P&gt;And if someone here tells you "you need 3 indexers" will you run and issue a procurement order based on this? And what if it happens to be undersized? Or the opposite - it will turn out to be mostly idle and you have paid throught the nose for the hardware?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 28 Jan 2026 17:17:17 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2026-01-28T17:17:17Z</dc:date>
    <item>
      <title>Indexer Sizing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-Sizing/m-p/757721#M120180</link>
      <description>&lt;P class=""&gt;&lt;SPAN&gt;We would like your guidance on how to calculate the required number of Splunk indexers for our environment.&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;Currently, our estimated data ingestion rate is approximately &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;1 TB per day&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;. We would appreciate it if you could advise on:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;The recommended number of indexers needed for this ingestion volume&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;I Have multi site deployment&lt;BR /&gt;#splunk&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Wed, 28 Jan 2026 10:23:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-Sizing/m-p/757721#M120180</guid>
      <dc:creator>msaleh7422</dc:creator>
      <dc:date>2026-01-28T10:23:12Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer Sizing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-Sizing/m-p/757722#M120181</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/315381"&gt;@msaleh7422&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;a quick and dirty evaluation is:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;one indexer every 200 GB/day og ingestion if you haven't a Premium App (ES or ITSI),&lt;/LI&gt;&lt;LI&gt;one indexer every 100-150 GB/day og ingestion if you have a Premium App (ES or ITSI).&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;in this second case, in ES training is described to use one indexer every 80 GB/day, but 100-150 GB/day is more correct value.&lt;/P&gt;&lt;P&gt;About CPUs, RAM and storage, you need a Capacity Plan that is very difficoult to do in Community: you need a Splunk Architect from a Splunk Partner.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;&amp;nbsp;Giuseppe&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jan 2026 13:59:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-Sizing/m-p/757722#M120181</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2026-01-28T13:59:51Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer Sizing</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-Sizing/m-p/757729#M120182</link>
      <description>&lt;P&gt;This is the kind of question you go to your local friendly Splunk Partner with, not some randoms on the internet.&lt;/P&gt;&lt;P&gt;There are many factors possibly affecting your environment size and overall architecture - search load, retention, HA requirements...&lt;/P&gt;&lt;P&gt;And if someone here tells you "you need 3 indexers" will you run and issue a procurement order based on this? And what if it happens to be undersized? Or the opposite - it will turn out to be mostly idle and you have paid throught the nose for the hardware?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jan 2026 17:17:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-Sizing/m-p/757729#M120182</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2026-01-28T17:17:17Z</dc:date>
    </item>
  </channel>
</rss>

