130 likes | 210 Views
BLËSK System Requirements. How to estimate your hardware needs. Some notes about virtualization. BLËSK can be installed in VMware or any other containers However, using virtualization, you will lose ~15% of performance
E N D
BLËSK System Requirements How to estimate your hardware needs
Some notes about virtualization • BLËSK can be installed in VMware or any other containers • However, using virtualization, you will lose ~15% of performance • You will have to compensate for this when estimating your hardware needs • This is true for any Operating System running in VMware • The penalty could change depending on the VMware version ( newer is better)
Application Performance Monitor • CPU consumption = 0.4% per process • Memory consumption = 2MB per process • 1 process = 1 service to check remotely • A process could takes from 2 seconds to 1 minute to complete • Has an interval of 5 minutes to complete its cycle of service checks
APMHow many processors do I need? Quick formula to calculate the number of CPUs required 0.4 X Number of services to check / 100 For example, we estimate the following: • 150 Servers to monitor • 10 services to monitor on each server 0.4 X 1500 / 100 = 6 CPU
APMHow much memory do I need? Quick formula to calculate the memory required 2 X Number of services to check / 1024 For example, we estimate the following: • 150 Servers to monitor • 10 services to monitor on each server 2X 1500 / 1024 = ~3 GB of memory
Network Performance Monitor • CPU consumption = 12% per thread • Memory consumption = 45MB per thread • 1 process handles 8 threads • Default NPM settings use 2 processes (16 threads) • Has an interval of 5 minutes to complete its cycle of device checks
NPMHow many processors do I need? Quick formula to calculate the number of CPUs required 12 X Number of threads / 100 For example, we estimate the following: • 200 network devices to monitor • 4 ports & 2 performance data graphs monitored for each device 12 X 16 / 100 = ~2 CPU
NPMHow much memory do I need? Quick formula to calculate the memory required 45 X Number of threads For example, we estimate the following: • 200 network devices to monitor • 4 ports & 2 performance data graphs monitored for each device 45 X 16 = ~720 MB of memory
SQL Server • CPU consumption = 5%per process • Memory consumption = 90MBper process • SQL can dynamically generate between 5 to 30 processes • SQL is used by 6 of the 10 BLESK programs • Disk I/O performance is important for the SQL server
SQL ServerHow many processors do I need? Quick formula to calculate the number of CPUs required 5 X Number of processes / 100 For example, we estimate the following: • 150 Servers to monitor with 10 services on each server • 200 network devices to monitor with 4 ports & 2 performance data graphs monitored for each device • 1 million logs received and stored every day 5 X 30 / 100 = ~2 CPU
SQL ServerHow much memory do I need? Quick formula to calculate the memory required 90 X Number of processes / 1024 For example, we estimate the following: • 150 Servers to monitor with 10 services on each server • 200 network devices to monitor with 4 ports & 2 performance data graphs monitored for each device • 1 million logs received and stored every day 90 X 30 / 1024 = ~2.5 GB of memory
What about the other programs? The other programs are not resource intensive and can share the CPUs & Memory without problems. Some points to remember: • NSM & ELM mainly depend on SQL server & Disk I/O performance • NTA depends on NIC speed (1 GB minimum) & kernel performance • ALCM depends on SQL server performance
Conclusion Our hardware requirements will be: For APM: • 6 CPUs & ~3 GB of memory For NPM: • ~2 CPUs & ~720 MB of memory For SQL: • ~2 CPUs & ~2.5 GB of memory Total: • 6 CPUs with 6 GB of memory Based on our estimates of the following: For APM: • 150 Servers to monitor with 10 services on each server For NPM: • 200 network devices to monitor with 6 components For SQL: • Disk I/O speed makes a difference in SQL server performance For the other programs: • Share the CPU & memory of the OS