No problem, just more of a curiosity about why a task that is sitting and doing nothing yet (we are in the middle of implementing something) would be rolling up minimal CPU. We figure it must be some heartbeat kind of checking.
Thanks for the direction, and guidance on the monitor impact. Don On Fri, Mar 19, 2010 at 3:00 PM, Ted MacNEIL <eamacn...@yahoo.ca> wrote: > >For instance, can I break down the CPU time into more > detail to see what is actually consuming these cycles? > > You need a monitor like OMEGAMON, or a GTF trace. > You also need a real reason to do it, because (Heisenberg) the monitors can > get in the way of what they're monitoring. > > Are you solving a problem, or are you just curious? > - > Too busy driving to stop for gas! > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
