Lansweeper 4.0 - performance issue

[Martin]

Hello,
I have a performance issue with the new version of Lansweeper.
I leave my PC on for night, with LS website open. In the morning, when I click on any LS link, I have to wait about 15-20 sec. for the page to display. But when it finally opens, all subsequent pages will open up immediately or with a 1-2 sec. delay which is absolutely fine. But after that, when I leave LS 'untouched' for ~30 min., the delay problem comes back; it's not that long this time, maybe 10 sec. but long enough to be a nuisance when you're having a user on the phone.
The version 3.5.2 was OK. The problem started with LS v.4 beta which was installed on a different physical server from scratch. I was hoping it's because of the overall poor performance of that server but I've recently installed LS 4 (from scratch) on the server where LS 3.5.2 used to be and the problem persists.
According to your suggestion I looked through SQL 2005 logs, and the server event logs but cannot see anything suspected. I checked Windows logs on my client workstation where I open LS website but no dodgy entries.
LS is installed on W2k3 Enterprise SP2, 12GB RAM, 2 x Quad Core Xeon E5430.
LS website uses windows authentication mode.
SQL Server 2005 where LS DB sits on is on a different physical server, same LAN (Gigabit).
I know it's not likely but from my point of view it looks as if the LS DB put itself in some 'sleep mode' after some time, or LS website 'forgets' my credentials and needs to authenticate me in the background first which takes the said couple of seconds...?
I've just removed AD windows authentication section from web.config to disprove the 2nd part of my supposition but I see no noticeable change.
Do you have any ideas?
Cheers,
Martin

[Anonymous]

We're also noticing the same issue. I will try to use some tuning, this looks like an SQL performance issue, when we access the reports dashboard it queries a lot of tables to fill in the dashboard data...

[Martin]

Right, here's what I've figured out so far:
I asked all LS users not to click on any LS links and after 1.5 hrs I asked one person to click on Dashboard reports which took him ~12 seconds. Then I refreshed mine which took ~1 sec. After another 1.5 hrs of not touching LS the scenario repeated in the same way but with a different person. We all use IE8. This proved the issue doesn't stay with my PC only, but still does not reveal the real reason.
Cheers,
Martin

[Martin]

I did that, thanks. And I'm still trying to spot the difference. When I use Chrome with IE plugin it seems to be running OK but I do not know if it's not because somebody else in my office keeps refreshing LS on their PC... I'll get back to IE8 and test it today. Then I'll let you know. Meanwhile I'll check IE8 settings as I noticed that some people in our office do not seem to complain, but again - this might be a coincident because somebody else might have used LS a moment before and "refreshed" the database or IIS or who-knows what else...
Cheers,
Martin

[Hemoco]

Maybe try to disable the "idle timeout" and lower the "startup time" (to 2 seconds)

[Martin]

Sure, no worries

[Hemoco]

Could you post all your application pool screenshots please.

[Martin]

I've no idea how to switch between classic and normal APP.
BTW - I've noticed that Idle timeout for APP is 20 min. (pic. attached). I changed it to 60 minutes but cannot see any improvement.

[Hemoco]

Looks like the sql queries take only 5 seconds.
Must be another problem (IIS related?)

Can you try switching between classic APP pool and the normal one?

[Martin]

Hi,
the LS database has 'auto close' option OFF.
If it comes to the sql profiler I did the following:
At 13:46:55 I pressed 'Dashboard reports' on LS website (I was on 'Departament overview'). After 13 seconds 'Dashboard reports' finally opened (13:47:08). Attached you will find the extract from sql profiler.
Getting back to 'Department overview' took me 0.5 sec., and opening 'All available reports' took 1 sec.
Cheers,
Martin

[Hemoco]

On the database server you can start the sql profiler for tuning.
This will show you the exact queries and the time it takes.

In the options of the database, can you check if "auto close" is set to "false"