Dino Viehland wrote:
You should see performance benefits especially if there's a large number of
types subclassed during startup. I'd also recommend ngen'ing the resulting
assembly.
We do ngen all our assemblies on install. Thanks for this info Dino,
very helpful.
Michael
Also clr.GetSubclassedTypes() will return you a list of types which
you have subclassed so far. It's designed to round trip w/
CompileSublcassTypes so you can do:
clr.CompileSubclassTypes('foo', *clr.GetSubclassedTypes())
which will write out all the subclassed types to foo.dll.
-----Original Message-----
From: [email protected] [mailto:users-
[email protected]] On Behalf Of Michael Foord
Sent: Monday, September 28, 2009 9:04 AM
To: Discussion of IronPython
Subject: [IronPython] clr.CompileSubclassTypes
Hello all,
We compile our Python files to assemblies using Pyc, for (amongst other
reasons) startup and performance benefits. Now that RC1 is out we are in
the process of porting to IronPython 2.6 (only two bugs reported so far).
Will we get any performance / startup benefits from also dumping the
.NET subtypes to disk, using clr.CompileSubclassTypes, and shipping /
adding references to those assemblies too?
Michael
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
_______________________________________________
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/blog
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
