<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 23, 2014 at 6:09 AM, Colin Putney <span dir="ltr"><<a href="mailto:colin@wiresong.com" target="_blank">colin@wiresong.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><br>
<br>
<br>
On 22 Apr, 2014 at 5:05:12 PM, Eliot Miranda (<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>) wrote:<br>
> ><br>
> In recent days I've written a script to build a Cog VMMaker image<br>
> from Squeak 4.5. See <a href="http://www.squeakvm.org/svn/squeak/branches/Cog/image" target="_blank">http://www.squeakvm.org/svn/squeak/branches/Cog/image</a>.<br>
> This has allowed me to run the current Cog VM against Spur side-to-side.<br>
><br>
<br>
</div>Nice. How much of the code that gets loaded is updating existing packages, rather than completely new code? Updating existing code usually involves lots of #become: and generates garbage...<br></blockquote><div><br>
</div><div>It's all new code. Here's the timing for just updating, but I'm not sure this is apples-to-apples because Kernel System and Collections differ between the two packages, and because there's a lot of network delay in this comparison:</div>
<div><br></div><div><div>McStalker.image$ time spurcfvm CogVMMaker-spur.image UpdateSqueakTrunkImage.st</div><div>real 0m45.886s</div><div>user 0m12.751s</div><div>sys 0m0.690s</div><div>McStalker.image$ time oscfvm CogVMMaker.image UpdateSqueakTrunkImage.st </div>
<div>real 0m35.929s</div><div>user 0m6.235s</div><div>sys 0m0.603s</div></div></div>-- <br>best,<div>Eliot</div>
</div></div>