Application very slow on HP9000,k360

[niranjan_8]

Hi,
We are using an ERP application (MFG-PRO Progress9.1D-Database), on HP-K Class server.

This application is extremely slow, can anybody give a hint on improving the speed of the DB. Cursor movements in OS level is OK, (in vi editor, login and $prompt and within the application).
But once I start any Database (perticularly-update) transactions, it takes ages to come out.

Is there any thing I can re-set/change parameters on the OS-side ??

Details of the server:
# uname -a
HP-UX singa B.11.11 U 9000/800 102410551 unlimited-user license
# model
9000/800/K360
# uptime
2:41pm up 11 days, 2:05, 3 users, load average: 0.69, 0.61, 0.68
# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 143360 89496 53456 63% /
/dev/vg00/lvol1 295024 59640 205880 22% /stand
/dev/vg00/lvol7 2097152 614448 1471768 29% /var
/dev/vg00/lvol6 1245184 1084816 159128 87% /usr
/dev/vg06/lvol1 4190208 2128 3926332 0% /u07
/dev/vg04/lvol1 4128768 472171 3428120 12% /u06
/dev/vg09/lvol1 8888320 6748336 2073172 76% /u05
/dev/vg08/lvol1 8888320 4623192 4131844 53% /u04
/dev/vg07/lvol1 8888320 5613812 3172226 64% /u03
/dev/vg11/lvol1 8888320 7112498 1720392 81% /u02
/dev/vg10/lvol1 8888320 6758454 2063360 77% /u01
/dev/vg00/lvol5 102400 2520 99168 2% /tmp
/dev/vg00/lvol8 1343488 1234208 108464 92% /opt
/dev/vg00/lvol4 1048576 832456 216120 79% /home
/dev/vg03/lvol9 4099465 77800 3611718 2% /disk4
/dev/vg01/lvol1 2051553 318 1846079 0% /db1
/dev/vg01/lvol2 2043577 925491 913728 50% /apps



Thanks
Niranjan Sangapur

[Ravi_8]

Hi

Looks like you have less swap space, try increasing the same

[Shaikh Imran]

Hi,
Could you post the following o/p

Login as root &
execute the following commands in order:
#script /tmp/perf
#uname -a
#model
#top -d5 -s10
#swapinfo -tam
#vmstat 2 5
#sar -q -M 5 10
#sysdef
#swlist -l fileset -a state
#kmtune
#echo "map selall info;wait infolog" | cstm
#exit
After exiting from the above you will have
a file named perf in /tmp directory
pls ftp that in binary mode,zip it &
attach it here.

Regards,

[Bill Hassell]

You are missing a lot of information here. Is the system running a 64bit kernel or just 32bit? If 64bit kernel, is MFG-Pro running in 64bit mode? Has this application, specifically the update, ever run significantly faster? There is no GO_SLOW or GO_FAST kernel parameter. It appears that you may be running Oracle too. If so, the database administrators may need to increase SGA to 1200-1500 megs. You should have a minimum of 4Gb of RAM on the system so you can take advantage of a large shared memory area. And the SQL code should run the explain option to see if there are missing indexes (which cause massively slow serial reads) or the indexes are badly unbalanced.

[Camel_1]

Run glance to see the realtime system performance, you may find out ideas whether it is related to cpu, mem, disk io, network, etc.

Simon

[niranjan_8]

Hi,
Thanks for the response.

Mfg/Pro is the only application on this server & this server is used for development purpose.(production server is HP-rp7410). The same copy of DB-application on rp machine runs without any issue. So DB-indexes should not be an issue

MfgPro is 32-bit on both the servers.
I could not find any GO_SLOW or GO_FAST parameters.

I will try changing swap space. (But again I do not have much space left).

I am sending some more info in on the server config.
Can you Pl. see the attached k360.txt?


THanks
nirnajan

[Bill Hassell · Accepted solution]

The information in the attachment shows the machine as virtually idle during some periods, and slightly busy the rest of the snapshots. Your machine has 1500 megs of RAM and 1500 megs of swap. However, Glance shows that a significant portion of the swap space is active which means lots of pages of processes have been written out. This is due to a lack of RAM.

Now it is certainly OK to have lots of interactive processes swapped out but if during the busiest periods, the page-out rate (vmstat or Glance) gets large, then the problems is simple: not enough RAM. Note that there is an enormous difference in processing power between the rp7410 and the K360. Since the K360 is so old (and you're running a 64bit kernel), you should double your RAM on the K360 to 3Gb or more. This is especially true if you see large page-outs when the system is busiest.