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 [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
