I can’t agree with this statement: “IronPython is actually doing quite a lot at startup time” http://ironpython-urls.blogspot.com/2009/08/good-mix-20-startup-time-inline-c.html If you are doing again and again the same thing and it affects users of the language why don’t you do it by some other way? Probably it could be possible to pre-compile the parts of CPython standard library IronPython uses. It is not a big deal to have couple more dlls required if you get 10 times faster startup time. Now for example it is not possible to write ‘unit tests’ by using IronPython. Just because ‘unit test’ is a code taking less than 10ms for run.
Aug
24
Pre-compile the parts of CPython standard library IronPython uses to make its startup time faster
2
Try putting an empty site.py in the same directory as your application (or modifying the default one) - see if makes any difference.
ReplyDeleteYou should also try compiling the Python standard library (using the Pyc IronPython compiler).
With the empty site.py the situation is much better, 3-4 times faster, thanks a lot!
ReplyDeleteWhat I didn't expect, IronPython loads C:\Python24\site.py (which is pretty big - 14K) w/o any request from my code. I didn’t expect it because it is possible to use IronPython even w/o CPython 2.4 installed, so I thought IronPyhon uses CPyhon only if I ask it.
Great! Thanks again. BTW it looks like with this option –S it is even faster :)