[Cuis-dev] CPUWatcher / Process Browser fix

Phil B pbpublist at gmail.com
Thu Aug 22 09:29:53 PDT 2019


Thanks!  That makes sense... I kept scratching my head asking 'why would
someone want this mashup of behavior?'  Your historical perspective
provides the 'why' though I do agree that it is likely no longer the
relevant use case.

On Thu, Aug 22, 2019 at 8:49 AM Juan Vuletich <juan at jvuletich.org> wrote:

> On 8/21/2019 1:38 PM, Phil B via Cuis-dev wrote:
> > The current implementation is broken... unless what was really
> > intended was to provide cumulative stats which doesn't seem right (or
> > useful) to me.  The attached changeset resets the stats each period,
> > uses a more sane default for the collection size, and increases sample
> > frequency to provide better resolution.
>
> I believe the original intent was for people to start CPUWatcher before
> doing some multi-process cpu-heavy stuff, and then stop it, and use the
> statistics to understand the behavior.
>
> But I agree that most people would expect what the CPU load monitor does
> on OSs. Your change is @ GitHub now. Thanks!
>
> Cheers,
>
> --
> Juan Vuletich
> www.cuis-smalltalk.org
> https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev
> https://github.com/jvuletich
> https://www.linkedin.com/in/juan-vuletich-75611b3
> @JuanVuletich
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20190822/ffcdcd75/attachment.htm>


More information about the Cuis-dev mailing list