I've had the same bash experience. Running a reasonably powerful Celeron 433 and Win 98, `ls -l' in a large (>10000 files) directory on a network drive can hang for >5 seconds before displaying the first record. Also, file name completion and process creation is agonizingly slow. I recently wrote a perl script to munge some text and structured it as two scripts: one to list the write files and send them over STDIN to the other, which sliced them up. I catted and piped the files to each other. Dropping the cat and pipe and combining the scripts into one more than doubled the speed of the operation. Of course, it's possible the file handling was taking more time than the munging, but in this case I doubt it.
Any guesses why bash crawls on Windows boxes?
Slashdot Mirror
I've had the same bash experience. Running a reasonably powerful Celeron 433 and Win 98, `ls -l' in a large (>10000 files) directory on a network drive can hang for >5 seconds before displaying the first record. Also, file name completion and process creation is agonizingly slow. I recently wrote a perl script to munge some text and structured it as two scripts: one to list the write files and send them over STDIN to the other, which sliced them up. I catted and piped the files to each other. Dropping the cat and pipe and combining the scripts into one more than doubled the speed of the operation. Of course, it's possible the file handling was taking more time than the munging, but in this case I doubt it. Any guesses why bash crawls on Windows boxes?