primitiveMillisecondClock usage (lots but why?)
John M McIntosh
johnmci at smalltalkconsulting.com
Wed Jul 2 05:14:14 UTC 2003
Well the issue is the smalltalk code is calling the primitive every 2-3
milliseconds.
This is above and beyond the VM calling the millisecond clock for
internal VM usage.
On Tuesday, July 1, 2003, at 06:18 PM, Tim Rowledge wrote:
> In message
> <9A6F6754-AAC6-11D7-BDC3-00306540A296 at smalltalkconsulting.com>
> John M McIntosh <johnmci at smalltalkconsulting.com> wrote:
>
>> Oh, and the other interesting issue is that we seem to call the
>> microsecond clock primitive a lot when
>> Squeak is just idle doing nothing... Say 6,186 times over 13.43
>> seconds.
> I'm pretty sure this is a very platform dependent thing and we probably
> ought to cut out all the clock trickery from the Slang code and stick
> it
> in platform code where it can be done however suits the machine. At
> least that way there would be no need to compromise one platform to
> suit
> another.
>
> tim
> --
> Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim
> Useful random insult:- She's a screensaver: Looks good, but useless.
>
>
>
--
========================================================================
===
John M. McIntosh <johnmci at smalltalkconsulting.com> 1-800-477-2659
Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com
========================================================================
===
More information about the Squeak-dev
mailing list
|