 |
» |
|
|
|
|
|
|
|
|
|
| Member icons |
| |
 |
HP moderator |
 |
Expert in this area |
|
| Member status |
|
 |
ITRC Pro |
| 250 points |
|
 |
ITRC Graduate |
| 500 points |
|
 |
ITRC Wizard |
| 1000 points |
|
 |
ITRC Royalty |
| 2500 points |
|
 |
ITRC Pharaoh |
| 7500 points |
|
 |
Olympian |
| 20000 points |
|
 |
1-Star Olympian |
| 40000 points |
|
 |
2-Star Olympian |
| 80000 points |
|
|
| » |
How to earn points |
|
| » |
Support forums FAQs |
|
| Question status |
 |
Magical answer
|
| Message with a response that solved the author's question
|
|
| Favorites status |
|
 |
Add to my favorites |
|
 |
Delete from my favorites |
 |
Thread closed |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
Gordon Fong
|
|
Aug 21, 2002 10:31:25 GMT
|
|
Hi all,
Right now doing performance tuning, is it normal / what cause this behaviour, that a process spend > 70% of time waiting SYSTM?
I sure CPU & Memory has enough resource ( > 3G memory free ) , for disks, sometimes it get to 100 spikes ( not last long, maybe 2 sec ), not obvious disks queue observer.
Bgds,
Gordon
PC : 0.0 Cache : 0.0 Wait Reason: SYSTM
Job Control: 0.0 CDROM IO : 0.0
Message : 0.0 Disk IO : 0.0
Pipe : 0.0 Graphics : 0.0
RPC : 0.0 Inode : 0.0
Semaphore : 0.0 IO : 0.0
Sleep : 0.0 LAN : 0.0
Socket : 0.0 NFS : 0.0
Stream : 0.0 Priority : 2.6
Terminal : 0.0 System : 75.9
Other : 0.0 Virtual Mem: 0.0
|
|
|
Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click
here
|
|
|
Sort Answers By:
Date or Points
|
|
|
Paula J Frazer-Campbell
|
|
Aug 21, 2002 12:12:08 GMT
Unassigned
|
|
Gordon
When this is at 70%+ what is the server doing - how busy?
Paula |
|
|
Gordon Fong
|
|
Aug 22, 2002 01:02:38 GMT
N/A: Question Author
|
|
Hi Paula,
Since it's Sybase replication server process, I have no idea on what that time this rep. server doing...
Bgds,
Gordon |
|
|
harry d brown jr
|
|
Aug 22, 2002 01:30:25 GMT
Unassigned
|
|
(1) What OS revision?
(2) What kind of hardware?
(3) Do you have glance installed? if not, purchase it and install it.
(4) is ems running?
(5) what are the top processes running?
(6) what does your swapinfo look like?
(7) what are your kernel parameters?
(8) What kind of disk sub-system?
live free or die
harry |
|
|
Gordon Fong
|
|
Aug 22, 2002 01:40:11 GMT
N/A: Question Author
|
|
Hi Harry,
Thx for yr address of Q.
1. It's running 11.00
2. N-class 8 CPU and 9GB memory
3. Yes have glance install, above screen dump for the suspect process is capture from Glance, and showing Wait reason : SYSTM on the sybase replication server process ( Reason I am interest in this process is coz we are experencing serious sybase replication delay )
4. Yes, we have EMS running
5. Top process is the Sybase server
6. sh: swapinof: not found.
<Host>:/#swapinfo -tam
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 1024 0 1024 0% 0 - 1 /dev/vg00/lvol2
dev 3072 0 3072 0% 0 - 1 /dev/vg00/swap2
dev 4312 0 4312 0% 0 - 1 /dev/vg01/swap3
dev 4312 0 4312 0% 0 - 1 /dev/vg01/swap4
reserve - 4122 -4122
memory 7133 4498 2635 63%
total 19853 8620 11233 43% - 0 -
7. Which kernel parms? There are so many..
8. It's using EMC Symm4 class.
Thx.
Bgds,
Gordon |
|
|
Bill Hassell
|
|
Aug 22, 2002 02:11:35 GMT
Unassigned
|
|
SYSTM means the program(s) are waiting for system calls. This is completely meaningless however since this is the way the program works and you have little control over that. A system call might be a query for the date or a request to open a file, etc.
Since the Rep-process is taking too long, has it ever run as you expect? Is there anything to compare with? This may be perfectly normal and only a redesign of the database will improve things. Without any 'norm' there's not much you can do to speed up a slow process. |
|
|
Paula J Frazer-Campbell
|
|
Aug 22, 2002 07:10:41 GMT
Unassigned
|
|
Hi Gordon
As said without a baseline to go by it is difficult to see if this is a problem.
If the server is very quiet the 70% of not very much is very little, but if busy then that 70% could be 70%b of a lot - therefore a problem.
Do a :-
grep -e KC_PARAM_NAME -e KC_PARAM_STATUS /var/sam/boot.config > /tmp/kern.info
Which will extract the kernel parms and please post the kern.info
Paula |
| | |
