Latency from "Finish" click to hourglass

[tsamost]

Hi, all

Did some searching, didn't see much relevant.

We're experiencing some latency in some of our environments, from the point when someone clicks finish (or chooses a value from aource/cascading/auto-submit prompt).  It takes some seconds, sometimes as little as 1-2, sometimes as many as 7-8, before the hourglass pops up.  Often times, the report returns more quickly than the time between the click and hourglass.

We have seen this on single-server installs, as well as multi-server installs.  We are a Windows shop for all the Cognos servers (IIS, App Tier, CM Tier, etc.).  The only major variance I've seen from other installs in my past is that ALL the Windows Servers are on VM's.

Has anyone else experienced this kind of latency, even on single-server installs?  Short of putting some kind of network sniffing tools against each server and the ports it uses/they use, I'm looking for ideas on where to look.

Thanks,

Todd Samost - American Tower Corp.

[bdbits]

I sometimes see a second or two, but not usually more than that. I think this is fairly normal, and is the client browser (javascript) gathering stuff and then sending it to the server. If it is longer and I bother to look, I have found a number of requests being processed by the server, i.e. a brief spike in load. I would have a look at your server logs as a starting point.

All of our Cognos servers are Windows servers on VMware, content store on Oracle, and a number of different database servers and vendors. Dev and test are single server, prod is dual servers. Honestly I do not see VMs as a factor. VMs these days perform very well with very little overhead.