<?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: Enterprise Security and Hardware Recommendation in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Enterprise-Security-and-Hardware-Recommendation/m-p/254946#M9276</link>
    <description>&lt;P&gt;Yes absolutely! &lt;/P&gt;

&lt;P&gt;ES uses a ton of saved searches, accelerations, summary reports, etc to work properly.&lt;BR /&gt;
This significantly increases the required hardware. Minimum specs are here: &lt;A href="http://docs.splunk.com/Documentation/ES/latest/Install/DeploymentPlanning"&gt;http://docs.splunk.com/Documentation/ES/latest/Install/DeploymentPlanning&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Most of the Splunkers I've talked to recommend you realistically plan for 24 CPU Cores and 48GB of RAM. It is certainly more CPU intensive than memory intensive, but don't skimp. Like you said the ES search head should be dedicated to that task.&lt;/P&gt;

&lt;P&gt;Good luck!&lt;/P&gt;</description>
    <pubDate>Mon, 21 Mar 2016 01:17:32 GMT</pubDate>
    <dc:creator>mwirth</dc:creator>
    <dc:date>2016-03-21T01:17:32Z</dc:date>
    <item>
      <title>Enterprise Security and Hardware Recommendation</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Enterprise-Security-and-Hardware-Recommendation/m-p/254945#M9275</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I have read through your hardware requirements for Splunk Enterprise. We will be purchasing the Enterprise Security (ES) app and have a dedicated Search server for ES. Question, are the hardware requirements any different for ES than the Enterprise?&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.1/Capacity/Referencehardware"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.1/Capacity/Referencehardware&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Mar 2016 19:24:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Enterprise-Security-and-Hardware-Recommendation/m-p/254945#M9275</guid>
      <dc:creator>brdr</dc:creator>
      <dc:date>2016-03-18T19:24:37Z</dc:date>
    </item>
    <item>
      <title>Re: Enterprise Security and Hardware Recommendation</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Enterprise-Security-and-Hardware-Recommendation/m-p/254946#M9276</link>
      <description>&lt;P&gt;Yes absolutely! &lt;/P&gt;

&lt;P&gt;ES uses a ton of saved searches, accelerations, summary reports, etc to work properly.&lt;BR /&gt;
This significantly increases the required hardware. Minimum specs are here: &lt;A href="http://docs.splunk.com/Documentation/ES/latest/Install/DeploymentPlanning"&gt;http://docs.splunk.com/Documentation/ES/latest/Install/DeploymentPlanning&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Most of the Splunkers I've talked to recommend you realistically plan for 24 CPU Cores and 48GB of RAM. It is certainly more CPU intensive than memory intensive, but don't skimp. Like you said the ES search head should be dedicated to that task.&lt;/P&gt;

&lt;P&gt;Good luck!&lt;/P&gt;</description>
      <pubDate>Mon, 21 Mar 2016 01:17:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Enterprise-Security-and-Hardware-Recommendation/m-p/254946#M9276</guid>
      <dc:creator>mwirth</dc:creator>
      <dc:date>2016-03-21T01:17:32Z</dc:date>
    </item>
  </channel>
</rss>

