1 00:00:02,510 --> 00:00:07,250 The final step and concluding the link specified in the document. 2 00:00:09,230 --> 00:00:14,870 Should be able to take you to the official documentation where you can download this. 3 00:00:15,770 --> 00:00:20,870 Manual, which will be handy while finalizing the architecture. 4 00:00:23,320 --> 00:00:24,910 Let us go through this link. 5 00:00:29,870 --> 00:00:39,410 So this is one of these links that are very useful while you are at the final stage of your Splunk adventure. 6 00:00:39,440 --> 00:00:42,590 This manual is known as Capacity Planning Manual. 7 00:00:42,620 --> 00:00:45,440 You can click download this manual as PDF. 8 00:00:45,470 --> 00:00:50,810 Make sure you are clicking on the top because if you download this, probably you will end up just getting 9 00:00:50,810 --> 00:00:53,630 the first page of the documentation or this topic. 10 00:00:53,630 --> 00:00:57,740 So make sure you click on download manual as PDF so that you get the complete. 11 00:00:58,900 --> 00:00:59,410 Manuel. 12 00:01:01,940 --> 00:01:10,160 So this is our capacity planning manual, which will be very handy while finalizing our Splunk architecture. 13 00:01:17,780 --> 00:01:24,650 And we have seen in our previous discussion we know what is the license cite number of indexes, equal 14 00:01:24,710 --> 00:01:31,160 number of searches, number of ave for order and whether to have a deployment server license manager. 15 00:01:31,190 --> 00:01:38,660 And also the hardware requirements like RAM CPU are required for each component of our Splunk. 16 00:01:39,980 --> 00:01:43,670 The storage requirement for indexers and IOPS. 17 00:01:43,700 --> 00:01:50,270 We will summarize all this and finalize the best fit architecture for the organization. 18 00:01:50,300 --> 00:01:55,310 Remember, always IOPS should be greater than 200. 19 00:01:55,940 --> 00:02:04,130 The RAM can vary from 12 to 64 GB based on the size of the architecture and the more cores. 20 00:02:05,030 --> 00:02:07,670 The more better for the searchers.