0 Replies Latest reply on Nov 15, 2017 9:54 AM by brentbo

    Network Atlas Performance Workaround


      We have a large environment with more than 70,000 elements under management. Under these circumstances, we've found Network Atlas slow and sometimes unreliable. However, we've discovered a simple workaround. Instead of signing into Atlas with our usual AD ID, which has no limitations to object view, we sign in with a SolarWinds ID, say DenverMapMaker. This special user has the same object limitation as the viewers of the map will have. In this example, the DenverMapMaker account can see only a tiny fraction of our overall objects. Connection time is cut dramatically, and Atlas performance become positively sprightly! Hope this helps -- Brent