[Vm-dev] getVMParameters broken
David T. Lewis
lewis at mail.msen.com
Fri Aug 6 15:05:15 UTC 2010
On Fri, Aug 06, 2010 at 04:24:10PM +0200, Adrian Lienhard wrote:
>
> Hi Henrik,
>
> On Aug 6, 2010, at 14:55 , Henrik Johansen wrote:
>
> >> primitiveVMParameter in the most recent version of VMMaker package was changed. Does the image-side code need to be adapted or is this a bug in the primitive?
> >>
> >> Thanks,
> >> Adrian
> > It's been changed to a microsecond clock value in recent VM's on Unix/Mac.
>
> Ah, I didn't notice the change of the clock. So, it's easy to fix. But the
> Windows VM doesn't have that (yet)?
Oops, I think that's my fault - I didn't coordinate with Andreas on making
sure the platform sources for this got updated properly last time around.
I think that the last widely advertised Windows VM was missing the necessary
updates as a result of this, and possibly is giving incorrect timing as a
result.
Can you try downloading the latest Windows VM from squeakvm.org and see if
the problem goes away? Using that VM with a Squeak trunk image I get output
like this:
'uptime 42h16m38s
memory 19,953,968 bytes
old 15,092,452 bytes (75.6%)
young 3,363,080 bytes (16.9%)
used 18,455,532 bytes (92.5%)
free 1,498,436 bytes (7.5%)
GCs 2,040 (74607ms between GCs)
full 2 totalling 86ms (0.0% uptime), avg 43.0ms
incr 2038 totalling 189ms (0.0% uptime), avg 0.0ms
tenures 7 (avg 291 GCs/tenure)
Since last view 1,652 (227ms between GCs)
uptime 375.6s
full 1 totalling 45ms (0.0% uptime), avg 45.0ms
incr 1651 totalling 134ms (0.0% uptime), avg 0.0ms
tenures 6 (avg 275 GCs/tenure)
'
The supposed 42 hours uptime is completely wrong, but the rest looks
reasonable.
Dave
More information about the Vm-dev
mailing list