comp.lang.idl-pvwave archive: archive » Re: Painfully slow IDL startup

Home » Public Forums » archive » Re: Painfully slow IDL startup

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Painfully slow IDL startup [message #52080 is a reply to message #52000]

Fri, 29 December 2006 13:55

JD Smith
Messages: 850
Registered: December 1999

Senior Member

On Sun, 24 Dec 2006 10:32:34 -0500, Richard G. French wrote:

> Answering part of my own question:
> It takes about 5 seconds for IDL to traverse the PATH +$IDL_DIR
> It takes about 15 seconds for IDL to traverse my local routines path, which
> includes the full astronomy library, the coyote library and a bunch of other
> routines harvested from the web, most of which are not used for the
> application I am developing now. So, part of the solution is to prune the
> PATH search. However, this doesn't work for interactive use - is there a
> quicker way to tell what lies in my path than
>
> setenv IDL_PATH +/usr/local/bin/idl/bin

I thought the IDL_IDL bridge specifically avoided searching the path all
over, since that might hit the network and result in slowness. Can you
confirm that it is truly crawling the path all over? It would also be
useful if the credentials of the parent IDL process could be passed to the
slave process without contacting the license server again.

JD

Report message to a moderator

[Message index]

		Re: Painfully slow IDL startup By: Wox on Mon, 25 December 2006 05:46
		Re: Painfully slow IDL startup By: Richard French on Sun, 24 December 2006 07:32
		Re: Painfully slow IDL startup By: JD Smith on Fri, 29 December 2006 13:55
		Re: Painfully slow IDL startup By: news.verizon.net on Tue, 26 December 2006 08:07

Previous Topic:	Moving XML elements between documents with IDL
Next Topic:	Re: New Eclipse-based IDE

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Oct 10 23:46:48 PDT 2025

Total time taken to generate the page: 0.64254 seconds