Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > User Device Tracker (UDT) > UDT - Knowledgebase Articles > UDT Business Layer Process has high CPU usage on an additional polling engine

UDT Business Layer Process has high CPU usage on an additional polling engine

Updated 21st Sept 2017


An additional polling engine is at 95% CPU usage. The Business Layer was split to run separate processes, the the UDT business layer is at approximately 50-70% CPU usage.


  • UDT 3.3


This seems to have been caused by the load on that server -- a combination of the number of jobs, ports, and large devices, and possibly SNMP delays.


  • UDT Scalability
    • UDT now supports:
      • 90K ports per polling engine 
      • 300K ports or more, maximum per instance (multiple polling engines) 
  • UDT_Job:
    • 300 Jobs L2 and L3 Jobs over last 3 days
    • Bringing back 70,000 ports


  1. Edit UDT Settings -> Layer 2 Polling and change the value to 1200 minutes.
  2. Edit UDT Settings -> Layer 3 Polling and change the value to 1200 minutes.
  3. EditUDT Settings -> SNMP pacing delay time and change the value to 1 (currently it is set 0 by default) on Device Tracker Advanced Settings page.
    If there are undesired side effects you may set this value back to zero.


Last modified