<div class="gmail_quote">On Wed, May 23, 2012 at 9:07 AM, Carles F. Julią <span dir="ltr"><<a href="mailto:carles.fernandez@upf.edu" target="_blank">carles.fernandez@upf.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks Vernon!<br><br><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Are these lags happening _when_ the .NET image is first started (from the command shell) or _after_ it starts, during operation. All .NET programs, written in any language, seem to take forever to get started initially. A lot of work has been done on IronPython to try to mitigate startup and import time lags. If the lags you are seeing are during a running image, there is something else afoot here.</blockquote>
</div><div><br> I amb having Huge lags when it runs the peace of code for the first time, after that the lag is not that big. But it still makes it pretty unusable for a real time interaction context.<br></div></div></blockquote>
<div><br></div><div>My guess is that it's .NET's JIT compiler. How do you execute the scripts? Are you compiling them and caching the results or re-executing them each time?</div><div><br></div><div>- Jeff</div></div>