From 6a53c6b4481af206acb07b6903d2f04fd4337382 Mon Sep 17 00:00:00 2001
From: Adam Ryznar <73100931+aryznar-splunk@users.noreply.github.com>
Date: Wed, 18 Aug 2021 18:01:00 +0200
Subject: [PATCH] Feature/add performance data (#86)

* fix issue with missing nslookup ADDON-38627

* Update install_full.bash

* add performance data
---
 docs/source/planning.rst | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/docs/source/planning.rst b/docs/source/planning.rst
index f5f9a007a..137d44180 100644
--- a/docs/source/planning.rst
+++ b/docs/source/planning.rst
@@ -35,3 +35,16 @@ Requirements
 * Splunk Infrastructure Monitoring specific requirements
     * Ability to create of obtain real and token
 
+Planning Infrastructure
+===================================================
+
+Single installation of Splunk Connect for SNMP (SC4SNMP) on
+machine with 16 Core/32 threads x64 and 12 GB ram will be able to handle up to 1300 SNMP TRAPs per sec.
+
+Single installation of Splunk Connect for SNMP (SC4SNMP) on
+machine with 16 Core/32 threads x64 and 64 GB ram will be able to handle up to 1300 SNMP GETs per sec.
+
+When planning infrastructure for Splunk Connect for SNMP (SC4SNMP) above limitations need to be taken under consideration.
+
+
+