This is just a guess ... The IronPython binaries that we release are signed and part of the loading process is signature verification. There is a great post on the .NET Security Blog that also talks about the performance...
http://blogs.msdn.com/shawnfa/archive/2005/12/13/502779.aspx Martin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Felix Sent: Monday, September 25, 2006 9:02 AM To: [email protected] Subject: [IronPython] Strange slowness when loading IronPython.dll Hi, I'm running IronPython 1.0 on Windows XP: IronPython 1.0.60816 on .NET 2.0.50727.42 Copyright (c) Microsoft Corporation. All rights reserved. >>> Something happened on my Windows XP box last week, and now when I start ipy.exe, the console window appears, but it takes ~15 seconds for the intro string and prompt to appear. Oddly enough, I found that this only happens with the Codeplex 1.0 binary distribution. If I build from the 1.0 source (release or debug using VS 2005 Professional) and run that, it starts up in ~1 second. The Codeplex binary *used to* start up on my box just fine about a week ago. I'm also embedding IronPython in a C# application, and I found that the first time the C# code accesses a class in IronPython.dll, the 15 second delay kicks in. The CPU isn't doing anything during the delay, and my antivirus software is not doing anything. It seems like it's related to the loading of IronPython.dll. Is there any way to trace or debug that loading process? Certainly, my workaround is the use the version I built myself, but this is a head scratcher. Any thoughts would be most helpful. Thanks, Paul _______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
<<attachment: winmail.dat>>
_______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
