Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Log & Event Manager (LEM) > LEM RAM and CPU Recommendations

LEM RAM and CPU Recommendations

Table of contents
Created by Craig O’ Neill, last modified by Craig O’ Neill on Sep 14, 2016

Views: 186 Votes: 2 Revisions: 5


This article provides brief information on LEM RAM and CPU requirements. 

As your LEM device count grows, the amount of data arriving to LEM grows too. The amount of Rules and filters may also grow. This will cause LEM to slow down. Your LEM will under perform.


All LEM versions



  • No unmatched data
  • No Windows Filtering Platform noise
  • Less than 500 rules firing per day
  • No agent connection issues
  • RAW (NDepth) database is disabled.


Note: If one or more of the above is true then you should resolve those issues with the SolarWinds Support Geek Team.


To calculate the amount of messages LEM you should run the Database Maintenance report and check the Overview on page 1 of that report.


Alternatively you can loosely calculate by running an nDepth search for 1 hour and multiply by 24:

15 → 35 million events/day 16GB of RAM & 4-CPUs
35 → 60 million events/day 24GB of RAM & 6-CPUs
60 → 90 million events/day 32GB of RAM & 8-CPUs
90 → 130 million events/day 64GB of RAM & 10-CPUs
130 → 200 million events/day 128GB of RAM & 12-CPUs





Last modified
09:27, 14 Sep 2016