→ 🚀What's New? Join Us for the Fall Product Launch! Register Now !

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
wgknowles
Engaged Sweeper II
Our server seems to take about 15 seconds to load up the web console after it has been sitting idle for a while. Subsequent page loads are much quicker.
I suspect that the connection b/t IIS and SQL is timing out, and the delay is a result of reconnecting.
To test this theory, I tried pulling up a .png file and indeed it came up instantly, whereas a page that required a SQL connection took ~ 15 secs.

Has this been researched before? Is there a best practice for improving performance?
2 REPLIES 2
Corbett
Engaged Sweeper
We experienced the same delay as described by wgknowles although ours is about 10-15 seconds.

My theory is that it has to do with the default settings of the IIS Application Pool that the Lansweeper ASP.NET application is running under. I have changed the following settings on the Application Pool and things seem better:
-Uncheck Recycle worker processes (in minutes)
-Uncheck Shutdown worker processes after being idle for (time in minutes)
Hemoco
Lansweeper Alumni
Do you get this large load time on all pages or just on the main page?

In sql server there is a "profiler" which can monitor all running queries and report the time it took to compute them.