Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

Home > Success Center > Log & Event Manager (LEM) > SolarWinds LEM Quick Start and Deployment Guide > Plan your deployment

Plan your deployment

Table of contents
No headers
Created by Caroline Juszczak, last modified by Caroline Juszczak on Aug 01, 2016

Views: 1,237 Votes: 0 Revisions: 5

Use this table to size your SolarWinds environment.

Deployment size is impacted by throughput of events and performance degradation.

Use the largest sizing that reflects your environment. For example, if you are running a small deployment and begin to notice performance degradation at 300 nodes, move to a medium deployment. As the number of nodes and data traffic changes over time, move to a deployment that supports your enterprise.

The hard drives are defined when the virtual appliance host is created. Installing LEM in a SAN is preferred, but high-speed hard drives (such as SSD drives) are required for high-end deployments.

When using original log (raw) storage, increase your CPU and memory resources by 50%. See your hypervisor documentation for more information.

Size of Deployment Hardware Devices

Small

(Receive 5M – 35M events and trigger up to 500 rules per day)

  • 2 – 4 core processors at 2.0 GHz
  • 8 GB RAM
  • 250 GB hard drive with 40 – 200 IOPS

Fewer than 500 nodes in the following combinations:

  • 5 – 10 security devices
  • 10 – 250 network devices, including workstation endpoints
  • 30–150 servers

Medium

(Receive 30M – 100M events and trigger up to 1000 rules per day)

  • 6 – 10 core processors at 2.0 GHz
  • 16 GB – 48 GB RAM
  • 1 TB hard drive with 200 – 400 IOPS

Between 300 and 2,000 nodes in the following combinations:

  • 10 – 25 security devices
  • 200 – 1000 network devices, including workstation endpoints
  • 50 – 500 servers

Large

(Receive 200M – 400M events and trigger up to 5000 rules per day) *

  • 10 – 16 core processors at 2.0 GHz
  • 48 GB – 256 GB RAM
  • 2 TB hard drive with 400 or more IOPS

More than 1,000 nodes in the following combinations:

  • 25 – 50 security devices
  • 250 – 1000 network devices, including workstation endpoints
  • 500 – 1000 servers

* The most successful large deployments receive up to 250M events per day.

 

 
Last modified

Tags

Classifications

Public