> Oh, I see. So they are cancelled before the time consumed shows up in
> the Top listing?
Well. It may happen that they come alive and die again right between two ProcessTop
breakpoints.
> What if all watchers had another attribute called 'stats_group'?
Well, I thought of a collection feature and I suppose data have to be collected by
Event internally where ProcessTop can ask for them.
> Ugh. Coding this is going to be messy.
Hm. Just for the moment, it happens that possibly a priority change to the idle loop
could solve my current load balance problem (this dynamic modification feature opens
a wide range of both tuning and debugging). I'm just trying and running the tests
and validating the results, this will take time. So IF SO there would be no need for
ME NOW, but honestly, thinking more generally ... I think this would be helpful. If
the (performance, memory, development, ...) costs are passable.
In my opinion, such a grouping would enforce display decisions. If grouping is used
and some members are still alive, where should they be displayed, with the group or
separately? There could be two modes ... hm, this is not simple, I agree.
Finally: I assume there is a reason not to provide "cancel" as well as "suspend" and
"resume"? And another sort suggestion: directive "ot" for "sort by type".
Jochen
P.S. ... bad news ... changed priorities did not solve the load problem ...
