This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
>From: Rick Kohrs <address@hidden> >Organization: SSEC >Keywords: 200108091622.f79GMP122796 McIDAS nexradir nexraget Rick, Sorry I couldn't get to this last week, but I was hosting a McIDAS training workshop. >I have been working on some composite radar images and have noticed that >my IMGLISTs are running 2-3X longer than my IMGCOPY commands. Here is an >example pair: > >IMGLIST NEXRAD/BREF1 FORM=EXP ID=MPX DEV=T RAD_PROD.DOC R >IMGCOPY NEXRAD/BREF1 RADCOMP/TEMP.1 SIZE=SAME STYPE=VISR ID=MPX > >My thought was that both getserver and dirserver would use the same >algorithm for searching/sorting and the getserver would have the extra >task of passing the data down to the client. They do. They go through the exact same code. >If this was the case, IMGCOPY should take longer to run. If you always do the IMGCOPY after an IMGLIST, then the files in the input dataset are cached by the OS. A second IMGLIST right after the first one should be as fast the IMGCOPY. I just ran such a test to one of our servers, and the results were as I expected. If you did the IMGCOPY first and the IMGLIST second, your results should be reversed. >Any thoughts? OS caching. Let me know if you disagree with this conclusion. Tom -- +-----------------------------------------------------------------------------+ * Tom Yoksas UCAR Unidata Program * * (303) 497-8642 (last resort) P.O. Box 3000 * * address@hidden Boulder, CO 80307 * * Unidata WWW Service http://www.unidata.ucar.edu/* +-----------------------------------------------------------------------------+