On Oct 1, 2004, at 6:42 AM, Mr Tea wrote:
For the record, I tried this at home and found that the script had not
actually caused a crash or indefinite hang. It was just working verrryyy
slowwwlyyy.
I built a timer into the script and left it running (getting info for a
network volume via a router over a 10/100 ethernet wire) while I went off to
do something else. In this case, the result showed a delay of 1219 seconds
(a little over 20 minutes) between asking for and getting the info. This
compares poorly with the already sluggish 23-5 second delay I see when
getting info for a volume on an internal drive. All this on a G4 867/1.5GB
RAM.
'info for' tries to be helpful in telling you the total size occupied by the folder you're asking after. It does this with a classic depth-first recursive walk of its file tree. If the folder is big, that takes time. If the folder is on a server, that takes time. If the folder is big
and on a server, it takes aeons.
I thought about adding an 'ignoring folder size' option to info for when I wrote it. I shoulda. Nag Nebel to do it.
Chris