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
Store

Is 5-7 seconds for spinning clock on web refresh normal?

Hello,

When the web map refreshes it goes blank for 5-7 seconds and I see a spinning wheel at the top center of the screen.

Is this normal?

Why can't it continue to display the previous information until the new refresh is ready to be displayed?

I'm running Orion NPM 9.5 SP4 on SQL Server express 2005 on a 2.8Ghz Xenon processor with 4GB of RAM.

Jay

Find more posts tagged with

refresh

display

web

Accepted answers

bshopp

Depending on multiple factors, such as the size of the background image and how many items you have on the map this can be seen.

So why would you want the old stale image to be displayed as it could no longer be accurate? To me it seems to me it could be mis-leading.

All comments

bshopp

Depending on multiple factors, such as the size of the background image and how many items you have on the map this can be seen.

So why would you want the old stale image to be displayed as it could no longer be accurate? To me it seems to me it could be mis-leading.

JayMeath

Howdy, Thank you for the quick response

There are about 80 items on the screen and the background is blank.

I understand the logic of the "old stale" image but since I've been staring at an "old" image for the last couple of minutes anyway a few extra seconds makes little difference.

From my perspective an extra 5-10 seconds of an old image is better than no image at all.

But, you answered my question and this operation "normal" and that's what I was trying to find out.

Thank you again for the reply.

Jay

savell

We don't use background images on our maps, and even for very small maps (5-10 devices with no embedded maps), the best reload performance we get is 5-7 seconds. Larger maps (with embedded map elements) don't appear to make a significant difference however.

We don't have database performance issues.

I have offered to provide any required diag's to the support team via some direct communication with the product manager. He is going to set-up a discussion with the development team - so I'm hopeful that some improvements can be made.

Dave.

savell

Just to illustrate a little further, on a complex map I have 200 elements for which status information is retrieved from the database (which also includes the embedded data elements).

I can see this from an SQL profiler trace - and can also see that this query takes <100ms to execute and return the 200 rows (and 90 columns).

The actual map source is cached in the local file system c:\Documents and Settings\Administrator\Application Data\SolarWinds\NetworkAtlas\Maps\Orion\localhost

It appears to me that most of the delay is actually in processing the data returned into the ORIONMAP file and doing the web server processing.

I wonder how much of the increased delay is as a result of the additional tooltip type information that is now returned and needs to be processed into the webpage at each refresh.

Dave.