| Re: Painfully slow IDL startup [message #52000 is a reply to message #51996] |
Sun, 24 December 2006 07:32   |
Richard French
Messages: 173
Registered: December 2000
|
Senior Member |
|
|
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
Thanks!
Dick
On 12/24/06 10:17 AM, in article C1B40433.9BC0%rfrench@wellesley.edu,
"Richard G. French" <rfrench@wellesley.edu> wrote:
> How can I speed up the startup of IDL? I'm running a license-servered setup
> on several OSX boxes. It takes 20-30 seconds to start IDL. When I try to set
> up PVM and IDL_IDLBridges, this results in intolerable delays, since I have
> this long a wait for each IDL process.
>
> I've also found, since running 10.4.X, that the startup time increases
> depending on how long the machine has been running. This is not just a
> problem for IDL - it also happens when running an astronomy image package,
> ds9, so we have to reboot the machine daily.
>
> I've commented out everything in my startup file, such as long path
> searches, and I've redefined IDL_DLM_PATH so that there are not even any
> DLMs to look for.
>
> It seems like this is an lmgrd issue - does anyone have any suggestions
> about how to turn on logging for lmgrd to see what the delay is caused by?
> Has anyone else seen this behavior? Thanks!
>
> Dick French
>
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
