On Mon, Oct 13, 2008 at 11:57 AM, Vernon Cole <vernondcole at gmail.com> wrote:
> Help me out here. I have seen many references to schemes to optimize import
> speeds on Iron Python. Isn't this an attempt to make up for the snail-like
> startup speeds suffered by all .net applications?
.NET has a substantial startup time, as does IronPython, and for small
applications, that will rule the day. However, for applications that
import in excess of 100 python files, that startup time starts to look
small. For me importing (starting timing only once IronPython has
started) takes a full 10 seconds on a 3.6GHz Core2. On a 2Ghz Pentium
4, this time triples. I suspect the resolver guys have a similar story
to tell.
-Dan