| Re: Painfully slow IDL startup [message #51996] |
Mon, 25 December 2006 05:46  |
Wox
Messages: 184
Registered: August 2006
|
Senior Member |
|
|
I don't know whether this applies for you, but I remember having a
slow IDL startup because IDL was searching for a printer which wasn't
there anymore (network printer went offline).
On Sun, 24 Dec 2006 10:17:23 -0500, "Richard G. French"
<rfrench@wellesley.edu> wrote:
> How can I speed up the startup of IDL?
|
|
|
|
| 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
>
|
|
|
|
| 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
|
|
|
|
| Re: Painfully slow IDL startup [message #52091 is a reply to message #52000] |
Tue, 26 December 2006 08:07 |
news.verizon.net
Messages: 47
Registered: August 2003
|
Member |
|
|
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
I haven't tried this, but perhaps you can improve your startup speed
by defining your !PATH to avoid caching during startup. From the IDL
help:
********************
Depending on the value of your !PATH system variable, you may notice
that some directories are being cached immediately when IDL starts up.
This will occur if your path definition string includes the
<IDL_DEFAULT> token, or if one or more entries include the "+" symbol.
In these cases, in order for IDL to build the !PATH system variable, it
must inspect subdirectories of the specified directories for the
presence of .pro and .sav files, with the side effect of adding these
directories to the path cache.
*******************
So I would guess that your would speed up your startup if you avoid
<IDL_DEFAULT> or the "+" symbol in your initial !PATH. Directories
would be cached only as they are subsequently searched. I think
you can still avoid the initial caching, if you use EXPAND_PATH to
expand your directories, e.g.
!path = expand_path('+/usr/local/bin/idl/bin')' + ':' + !PATH
Of course, you could also disable path caching completely, but that
would impose a much larger time penalty in subsequent procedure calls.
Finally, your reported times seem much too long to be due to a normal
PATH search problem, and suggest that there might be something else
going on (like the previous suggestion of searching for a printer).
--Wayne
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
