<br><br><div class="gmail_quote">On Wed, Jul 2, 2008 at 11:07 AM, John M McIntosh <<a href="mailto:johnmci@smalltalkconsulting.com">johnmci@smalltalkconsulting.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
[SNIP]</blockquote><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Ya, there is exactly one place in the VM where the processor switch happens. In the past I tinkered with it to add some slots to Process to track wall clock time by process.<br>
At that time was I was thinking gee we could count bytes allocated and other things like socket usage etc, thus providing a bit more process consumption statistical data for<br>
Squeak threads ala unix processes.<font color="#888888"></font></blockquote><div><br>Please maintain an option that keeps process context switches as fast as possible. I'm interested in Erlang style architectures and how they might be implemented in Smalltalk. Hydra+Cog+Newspeak would make a really nice platform for Erlang-style applications. <br>
<br>-david<br></div></div><br>