nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Multiple virtually identical maps in Network Atlas and Change log for Atlas 1.0.6

drhodes

If I have multiple maps that are virtually identical in Network Atlas (have a newer map with same/more nodes than the original) would this slow down NPM because it is having do device status checks on both maps? (do not use the old maps in the web console).

Also, is there a change log for the newest version of Network Atlas 1.0.6

Find more posts tagged with

Accepted answers

All comments

michalB

Statuses of devices on a map are read from database only when the map is being displayed. So having a map stored only in your database does not influence the overall website performance (actually, it does, but this is something you would not notice).

I do not see any change log for Orion 9.5 SP5 on thwack, I will ping PM for this.

bshopp

SP5 was only needed for a module support, this should be good -

drhodes

Actually, I was looking for the NetAtlas 1.0.6 that was provided with 9.5.1

savell

I don't quite agree with the "you would not notice comment".

One of our outstanding issues is the I/O performance of the C: (i.e. system drive) drive on our web servers - as a result of the cached maps that end up in this drive (and the continual folder and file scanning that occurs). It seems to be a significant cause for the map load slowness. We have two SLX implementations with vastly different map counts on each, so while it a little apples and oranges, we think the observations are valid in terms of map performance behavior.

We had a support ticket open on this one - and the indication provided was that it was one of the performance issues addressed in v10 (I had hoped it was covered in the Network Atlas performance improvements within the "what we are working on" thread).

As always, I'm working with incomplete information - it would be nice to be corrected with some additional detail regarding the cause of the I/O load on the C: drive and it's relationship to cached map files.

Dave.

michalB

All maps are stored in database and are synchronized to a client on demand. The client may be a web server or an instance of Network Atlas. So the first load takes quite long, because all the maps need to be downloaded. However, when a map is being displayed on the website for the second time, the maps are already on the client's drive (in the TEMP directory) and only their time stamp is compared. Therefore, the map that is not being displayed, does not significantly influence the overall website performance.