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

Speeding up website response times

Hi,

I can see others have wondered about really slow response times when accessing the different graphs, charts, etc. in Orion.

My personal experience has been load times of 30+ seconds from typing in username and password until the default network summary paged appeared. Getting tired of this waiting time, I sniffed some of the traffic and didn't find many clues. Then I thought "DNS" and reverse lookup of the client IP addresses and *kapow* ... after adding a reverse zone to the DNS server used by the Orion server (in this case this server also hosts its own DNS since it's a domain controller) and adding the IP addresses of the clients accessing the server to the reverse zone, load times for the network summary page went down to just 2 seconds.

So ... the FAQ mentions antivirus software as a cause for slow website response, but in fact it seems the lack of reverse DNS for the clients accessing the site means even more.

BTW: This is probably not due to the way Orion is coded. I am guessing it's got more to do with the way IIS logs access. Disabling IIS logging might yield similar results but I wouldn't recommend it.

Christian

Find more posts tagged with

Accepted answers

All comments

I found this article at Microsoft which tells how to ENABLE DNS lookup for IIS. By "reversing the polarity" one could make sure the DNS is disabled

support.microsoft.com/default.aspx

Which comes with the following warning

Warnings
Enabling reverse DNS on your IIS server can affect the performance of your Web server and DNS servers. Some examples are: • Resources such as CPU utilization and network bandwidth may be taken up.
• Client requests can take longer to process.

Also found if you are restricting access by DNS domain, you will be causing Reverse DNS Lookups.

support.microsoft.com/.../

BK
Nobody Special

mjhamilton

I find this really interesting... I plan to test this tomorrow.. will report back my results.. the first page is a pain to load up but the other pages are ok.. I just thought it was and IIS bug..... [;)]

Martin J. Hamilton... lost in a sea of snmp...

CEllsworth

Went from 7 secs per page to about 4. Login still takes to long.

Maybe if we used a dedicated sql server the speed will increase. (Im still not impressed).

bleearg13

I have noticed that if your default summary page has a lot of devices it needs to get information on, such as a network map or a list of nodes, this greatly increases the number of seconds it takes to log in. By reducing the amount of devices that your summary page is getting info on will reduce your login time greatly.

Seraphym

I had the same problem. My startup-page took more than 1 minute to load

My solution : create a custom startup-page with only the most important devices (i use the 6500 catalysts from our backbone) -> it will load really fast ! time to load now : 2 seconds

hope this helps, it worked for me.

mihi est propositum in taberna mori

Mithrilhall

How many nodes, interfaces and volumes are you monitoring?

If you're over a certain number of devices it is highly recommended to move your SQL Sever to a dedicated machine. Also, you might need a second polling engine.

We're currently looking at these two options and our numbers are:

478 Nodes, 11412 Interfaces, 127 Volumes, 12017 Total Elements