Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Art S. Kagel — — source: Informix-list mailing list archive (1991-1998)
David Williams wrote:
>
> In article <36125DF0.54B3@netcomuk.co.uk>, Neil Truby
> <ntruby@netcomuk.co.uk> writes
> >kroy@Celestica.com wrote:
[SNIP]
What is the apps PDQPRIORITY? What is MAXPDQPRIORITY? It may be that
that one app is hogging all available resources. The onstat -g ses
that Neil suggested will show a large number of threads and memory
segments in this case. Remember that the actual granularity of
resources is NOT the 1% that the PDQPRIORITY parameter seems to allow.
If you have 4 CPU VPs a task running PDQPRIORITY=10 will use 25% of
your CPU resources since you cannot allocate less than one CPU VP at a
time. Therefore four copies of such a beasty running concurrently can
hog close to 100% of the server especially if the working dataset it
small enough to fit in the BUFFER cache so the tasks never go into I/O
wait.
> Run Art Kagel's dostats.ec from www.iiug.org
> [Thanks for the mention in the version history Art!!!]
Credit where it's due David. You are welcome and thank you.
Art S. Kagel
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.