Re:
> I have a job that is executing but is doing so VERY slowly. I have looked
> at it in SOS and it shows that it's primarily in either a CPU wait or a MSG
> wait. I recalled that Stan had provided some info awhile back about using
> SHOT [2.32] - LPS Toolbox [A.07a] (c) 1995 Lund Performance
I'd get a newer version...that's about a year old, and doesn't know about
7.0.
> Highest PIN in use = 320, max pin possible = 8190
>
> ? PIN CPU Process Name Pri Q Delta % Ic Wait State
>
> - --- ------ -------------------------- --- - ----- --- --
> --------------------
> 192 m 414 NBSPOOL.PUB.NETBASE 253 E 582 34 On (executing)
> 201 s 4426 WH.WHII.TAURUS 152 C 273 16 Nn (executing)
> 317 s 384 CI.PUB.SYS 152 C 104 6 Nn TIMER
...
> (Warning: MI on)
>
> SHOT [Delta]: ADM +WAITSEMPIN
> ? PIN CPU Process Name Pri Q Delta % Ic sPIN Wait State
>
> - --- ------ -------------------------- --- - ----- --- -- -----
> --------------
> 201 s 4440 WH.WHII.TAURUS 152 C s 14 41 Nn READY
> 202 s 1755 NBSPOOL.PUB.NETBASE 152 C 769 2 On MESSAGE
> 206 303 JSMAIN.PUB.SYS 152 B Nn
> MsgPort#-33048
> 207 852 SHOT.PUB.LPSTOOLS 152 C 122 Nn (executing)
>
> The PIN for my job is 201, however I'm not sure how to interpret what I've
> found. I'm on 6.5 PP2 on a 996/800.
Your process, 201, isn't waiting ... it's ready to run in the second case
(but, having used about an hour and a half of CPU time, it's probably waiting
for any of at least 8 other less-CPU-intensive processes to give up the CPU
first) (In the first snapshot, we saw 201 executing on one of the CPUs,
and the system has 8 CPUs)
If you want to know what it's *doing*, you can do:
Shot: TRACE 201
however, if it's spending time in its code (as opposed to MPE code), the
stack trace won't be as much use, because we don't have access to the symbols
(the names of the procedures). So, you can do:
run wh.whii.taurus; debug
pin #201; tr, i, d
and enter the "pin #201; tr, i, d" several times over several minutes, to get
an idea of what's going on.
and, eventually:
abort
(because you probably don't really want that copy of WH to run)
The "run <program>;debug / pin; tr" combo will show you the procedure
names in the program you're interested in!
Stan Sieler [log in to unmask]
www.allegro.com/sieler/wanted/index.html www.allegro.com/sieler
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
