Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

GroupedNodes Causing Slow Web Page Loading

We are up to almost 1000 nodes now, and our solarwinds web page is taking up to 15 seconds to load. After some reasearch, it appears that the GroupedNodes.Resource is causing the slowness. We have 2 levels of grouping. We really like the ablility to view the nodes in this manner, however the slow loading page is getting on our nerves.

Has anyone tried using an ASP tree component instead of the way GroupedNodes.Resource does it?

Find more posts tagged with

Accepted answers

All comments

iunderwo

The grouping doesn't necessarily add a lot more overhead to the page, per se. However, since it does provide the whole list every time, it does get to be rather intense.

I gave up on that approach for the main page and largely rely on search functions and a list of down nodes.

// Ian Underwood - Service Management
// Level 3 Communications

pancamo

We Really Like the treeview on the main page. It shows exactly where the problems are located...

I did "Detached Resource" on all the Main Page Resources. All of the resources take less than a seconds to refresh except for the Treeview. The Treeview takes at least ~10 seconds. We use a custom property structure like

LAN (Node Type)
ATLANTA (City)
HOUSTON
ROUTER (Node SubType)
routerXXX
SWITCH
LONDON
WAN
SERVER
HOUSTON
WINDOWS
dc01
UNIX
STORAGE
WEB

The SQL to get the node names take < 1 second. The slowness is with the DO loop that builds the treelist.

I'm working on a 3rd party ASP tree component that will build the tree in < second which should fix the slowness problem. Hopefully SW will include a better tree solution soon.

quote:Originally posted by iunderwo

The grouping doesn't necessarily add a lot more overhead to the page, per se. However, since it does provide the whole list every time, it does get to be rather intense.

I gave up on that approach for the main page and largely rely on search functions and a list of down nodes.

// Ian Underwood - Service Management
// Level 3 Communications