[Info-vax] HIBertanting DECthreads process accrues CPU time.

[VAXman- at SendSpamHere.ORG]

In article <ij9i91$s4n$3 at news.eternal-september.org>, glen herrmannsfeldt <gah at ugcs.caltech.edu> writes:
>VAXman- wrote:
>> In article <422e7e27-0a8a-45a6-a721-b6cf3addedb6 at u17g2000yqe.googlegroups.com>, John Wallace <johnwallace4 at yahoo.co.uk> writes:
>
>>>Is it really accruing CPU time at an alarming rate? Or is the usually
>>>reliable mechanism for reporting CPU time falling victim to odd
>>>behaviour in this case, and causing unnecessary alarm?
> 
>> Reality or spectre, seeing an otherwise *IDLE* process accruing CPU time
>> is not acceptable to me and is likely to cause alarm with customers.
>
>I am not sure at all how different system charge for the CPU time
>needed for paging.  It would seem fair to charge for the page out
>time, even when one is idle.  That should be fairly small in CPU
>time, though.

The most recent restart with runaway:

 Elapsed CPU time:          0 00:00:09.78
 Connect time:              0 00:03:51.07


    State               HIB                 Working set                340
    Cur/base priority  14/12                Virtual pages            14969
    Current PC FFFFFFFF.805FCEB0            CPU time         0 00:00:09.78
    Current PSL         00000000            Direct I/O                  55
    Current user SP     001FBA30            Buffered I/O                24
    PID                 21800981            Page faults                286
    UIC                 [SYSMGTGRP,SYSTEM]  Event flags           80008000
                                                                  80000000

If VMS is charging me 9 CPU seconds for the little paging that's been done,
I'd think anybody here would consider that price gouging!

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.