I suspect that some of your type libraries are stored on a network share and not local. This may make reading the library rather slow.
You may want to use a tool like Process Monitor (from Sysinternals, now Microsoft) to see which files are being accessed by the Perl process during this call. Cheers, -Jan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: September 5, 2008 2:56 AM To: [email protected] Subject: perl starts very slow using WIN32::OLE Hi, I have a real big perl program - it runs already for a couple of years and I am always adding some features. So since a few days it needs over 2 Minutes to start!!! I did a profiling and the problem seems to be the Win32::OLE::Const:::_Typelib So here is the actual output of the profiler: ################################# %Time Sec. #calls sec/call F name 68.28 137.9805 777 0.177581 Win32::OLE::Const::_Typelib --> so perl needs 137 seconds for 777 calls!!! --> the first line (Win32::OLE operating in debugging mode: _Unique => 1) when starting the programm comes at once and after that I have to wait for a while => seems that the first call to Win32::OLE::Const::_Typelib need so long ???. Is perl searching the lib? And this is the output of the same program months ago: ################################# %Time Sec. #calls sec/call F name 1.12 0.0794 686 0.000116 Win32::OLE::Const::_Typelib I'll be thankfull for any idea! Cheers Armin Armin Nolte Database-Marketing Deutsche Behindertenhilfe - Aktion Mensch e.V. Heinemannstr. 36 53175 Bonn Tel.: 0228-2092-233 Fax: 0228-2092-222 www.aktion-mensch.de
_______________________________________________ Perl-Win32-Users mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
