Dino Viehland wrote:
I would actually suggest compiling the standard modules as well as your code
and then ngen them both on install. You can compile the std modules into their
own .dll so the user can always replace them w/ their own version (or they can
simply delete the DLL and then pick up the .py files).
The reason I suggest this is with the bits on my machine I'm seeing massive
import speed ups w/ pre-compilation + ngen (e.g. 3x or so).
Wow - that's great news. It makes the transition to IronPython 2 all the
better for Resolver One.
In the next release of Resolver One (1.3) we have almost halved startup
time - all down to the work of Kamil Dworakowski who has implemented
various improvements including a very clever parallel import system
(complete with import graph analysis) that I'm sure he'll blog about soon...
Thanks
Michael Foord
And decimal does import a lot more - but the real working set hit came from
publishing all the SymbolIDs for every precompiled module - once for each
module - on startup! A small oversight :)... But there were a few other areas
that could use some improvement as well.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord
Sent: Monday, September 29, 2008 2:30 PM
To: Discussion of IronPython
Subject: Re: [IronPython] What happened to source drops?
Dino Viehland wrote:
They're checked in so they'll be in the next source push. There are some perf
problems that I have fixes for though that aren't checked in (e.g. import
decimal in pre-compiled currently allocates ~550MB of memory) - but you should
be able to do functional testing :). I'll should have the pre-comp perf fixes
in this week.
Cool - thanks. 550mb for one module - wow. Good job we aren't intending
to precompile the Python standard library modules we're using. Having
said that we have quite a chunk of Python source we would like to
compile - I wonder if a 4gb address space will be enough. I think we
will be reluctant to move to 64bit oses only... ;-)
Michael
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Foord
Sent: Monday, September 29, 2008 2:15 PM
To: Discussion of IronPython
Subject: Re: [IronPython] What happened to source drops?
Dino Viehland wrote:
It looks like the script which automatically publishes the code has stopped
publishing the updates. Dave's OOF today and I can't find the original
instructions but Sri's looking into it.
Cool. If you get the compiling packages fixes into a code drop please
let me know so that we can start testing them early.
Thanks
Michael Foord
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Eloff
Sent: Monday, September 29, 2008 1:23 PM
To: Discussion of IronPython
Subject: [IronPython] What happened to source drops?
I'm noticing that the last source drop was the beta 5 release two weeks ago.
I don't mean to pressure you guys, but I am looking forward to the
next source release, which seems to have the delegate regressions
fixed. Any (vague) idea of when regular source drops will be resumed?
By the way, I built IronPython b5 for Silverlight RC0, and I had to
modify Microsoft.Scripting.Silverlight.ErrorFormatter:
- HtmlPage.Document.GetElementsByTagName("body")[0].AppendChild(target);
+
((HtmlElement)HtmlPage.Document.GetElementsByTagName("body")[0]).AppendChild(target);
I'm not fully sure how this code compiled in the first place, as
ScriptObject never had an AppendChild method. Probably this code has
already been fixed, but it's worth checking anyway.
-Dan
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/
http://www.trypython.org/
http://www.ironpython.info/
http://www.theotherdelia.co.uk/
http://www.resolverhacks.net/
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/
http://www.trypython.org/
http://www.ironpython.info/
http://www.theotherdelia.co.uk/
http://www.resolverhacks.net/
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/
http://www.trypython.org/
http://www.ironpython.info/
http://www.theotherdelia.co.uk/
http://www.resolverhacks.net/
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
