Server Response time on Actuate

[Akihiro Noma]

Hi:

We have two K420 Servers which are basically identical. We loaded the third party software called Actuate e-Reporting Server and Reportcast.

Response time on detail report viewing on one of the server is 26 seconds and the other 1 minute and 13 seconds.

I am not too sure where to start to look for the possible bottleneck. Can anyone give me some suggestions to where I can start to look?

Also if there is anyone out there who uses Actuate, I would like to get in touch with you..

Thanks for your help!

[MANOJ SRIVASTAVA]

Hi Akihiro Noma


We use a tool called as sarcheck . Essentially if you are using to check for th systems performance the tools like sar / top/ vmstat and Glance do it all . Interms of system activity and the response time the best place to start is to check for the following :

1. TOP ( load avg , top mem consuming proc
ess )
2. Glance it gives a nice graphical o/p interms of CPU / Memory/Disk /Network Util.
And that is what you need to look to find the bottle necks .

3. Sar will give you the best resports and is also the simplest to use.

All the best

Manoj Srivastava

[harry d brown jr]

There are many different things that can cause this type of issue:

Physical differences in hardware, including having the same hardware but in different slots. Check to make sure you have a properly terminated SCSI's. Make sure you have the "exact" same hardware, because a SCSI-1 device is different than a SCSI-2, etc...

Check your Kernel parameters, Filesystem's (the VG's), Patch's (swlist), and applications.

Check to see if one system has nfs mounts, mirroring, or striped disks.

[Sridhar Bhaskarla]

I do not know about Actuate. There are some good tools like MWA, BEST/1 that can be configured to check the wellness of the system. You can group the processes together called workloads and then calculate the WAITTIMES per workloads.

There are response times per each component like CPU, DISK, Network, IPC etc.,

SAR is also a good tool if we do not plan to use other softwares

iostat, vmstat and top are also helpful.

CPU

sar -u, sar -q

Memory

sar -w

kernel, IPC and system calls

sar -v, sar -m, sar -c

Disk

sar -d and sar -b

It doesn't give much information about network.
You have to use lanadmin to check for errors on the interface

-Sridhar