×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From*Job Waits White Paper*:
_
ftp://public.dhe.ibm.com/services/us/igsc/idoctor/Job_Waits_White_Paper_61_71.pdf_
1.0 Running and Waiting
All “units of work” in a system at any instant in time are in one of
three states:
*Q. CPU Queuing:* ready to use CPU, but waiting for a processor to
become available (a.k.a. “ready”, “CPU queued”, "CPUq")
*C. Dispatched CPU: *(a.k.a. “dispatched to a CPU/processor”, “on a
CPU”, “running”, “running and sharing a processor”).
Note: Dispatched CPU time very frequently differs significantly from CPU
utilization or CPU time due to multithreading (hardware or software),
virtual processors, or background assisting tasks. This is normal! More
on that later.
*W. Waiting* for something or someone (a.k.a. “blocked”, “idle”)
I think you can take a look at PDI (Performance Data Investigator). It's
interesting how PDI groups wait buckets for better understanding.
El 24/7/18 a las 12:00, Steurbaut, Richard escribió:
Hello, We have a job that is running longer and shows a good amount of time
being spent in dispatched cpu sharing/waiting. Would anyone be able to
explain what dispatched cpu sharing/waiting means. Thanks !
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
