[IronPython] Performance Issue

Dino Viehland dinov at microsoft.com
Wed Nov 12 19:56:52 CET 2008


CompiledCode exposes the default scope it executes in via the DefaultScope property.  So hold onto the result of source.Compile and after executing the code you can grab the scope and use it to get your variable.

From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Wilfredo Lugo
Sent: Wednesday, November 12, 2008 10:25 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Performance Issue

Thanks.

But then If I don't use my defined scope, how I could fill my function delegate?

Right now I am using :

Microsoft.Func<string, string, string, string, int, int> func = scope.GetVariable<Microsoft.Func<string, string, string, string, int, int>>("interpolate_start");

If I use engine.GetVariables<Func<....>() I still need to pass a ScriptScope to it.  How do I get the default scope (from ScriptEngine or ScriptSource) to be able to get the delegate?

regards,

wilfredo
On Wed, Nov 12, 2008 at 2:01 PM, Dino Viehland <dinov at microsoft.com<mailto:dinov at microsoft.com>> wrote:

Instead of doing:



            ScriptScope scope = engine.CreateScope();

            Console.WriteLine(DateTime.Now);

            source.Execute(scope);



do:



                source.Compile().Execute()



and your code should then run in an optimized default scope for the code - just like it does at the command line.



From: users-bounces at lists.ironpython.com<mailto:users-bounces at lists.ironpython.com> [mailto:users-bounces at lists.ironpython.com<mailto:users-bounces at lists.ironpython.com>] On Behalf Of Wilfredo Lugo
Sent: Wednesday, November 12, 2008 9:29 AM
To: users at lists.ironpython.com<mailto:users at lists.ironpython.com>
Subject: Re: [IronPython] Performance Issue





I run the script directly from ipy.exe and it basically behaves pretty similar to python.exe (it always took one second more, but I could live with that).  Here is the output:



$ date +%M:%S;./ipy.exe interpolate.py;date +%M:%S

17:36

WARNING: desired starting time (Tue Jan 01 00:00:21 2008) prior to time of first

 data point (Tue Jan 01 00:00:32 2008), current line: 9411

 series: 3D

force==False, exiting..

17:41



So, the problem is on the DLR side.  Any clues?



-------------------------------------------------------------------------

How does python.exe compare directly to ipy.exe?  That is, try running "date +%M:%S;ipy.exe interpolate.py;date +%M:%S" instead of using the DLR hosting APIs.

Thanks,



Dave

From: users-bounces at lists.ironpython.com<http://lists.ironpython.com/listinfo.cgi/users-ironpython.com> [mailto:users-bounces at lists.ironpython.com<http://lists.ironpython.com/listinfo.cgi/users-ironpython.com>] On Behalf Of Wilfredo Lugo

Sent: Wednesday, November 12, 2008 8:32 AM

To: users at lists.ironpython.com<http://lists.ironpython.com/listinfo.cgi/users-ironpython.com>

Subject: [IronPython] Performance Issue

_______________________________________________
Users mailing list
Users at lists.ironpython.com<mailto:Users at lists.ironpython.com>
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20081112/08e492f9/attachment.html>


More information about the Ironpython-users mailing list