RE: Simple bash script is slow to execute - appears to be time spent starting commands like ls

Larry Adams wrote: The problem as I see it is Windows. For example, only 10 iterations caused over 65k file and registry reads. I have attached the output from SysInternals Process Explorer for your edification. The only fix for this is Linux. I still use Windows for development and "LOVE"

RE: Simple bash script is slow to execute - appears to be time spent starting commands like ls

> Good point. You might also try running a shorter version of the loop > (100 iterations rather than 1) using /bin/true rather than just > true. I expect the performance difference to be even more dramatic. It was a factor of 100 - see response on other thread branch. >> I also noticed that

RE: Simple bash script is slow to execute - appears to be time spent starting commands like ls

Bryan Thrall wrote: You're right about true being built-in, but we still don't know from your examples whether the problem is from forking or from IO. Try replacing 'true' in Jeremy's loop with '/bin/true'. Comparison between the two should give us an idea of the forking cost, without IO getting i

RE: Simple bash script is slow to execute - appears to be time spent starting commands like ls

Jeremy Bopp wrote: How about we try to boil this down a little further? Try running the following on your various systems and compare the results: time for n in $(seq 1 1); do true; done I'm hopeful that this should help eliminate IO as a bottleneck in your comparisons. Maybe someone else

RE: Simple bash script is slow to execute - appears to be time spent starting commands like ls

I wrote: Let's say we focus on the echo | cut slowness I mentioned earlier. This is independent of the CWD and doesn't cause the explorer.exe spike but is still 200 times slower on my Vista laptop than on a low-powered Linux server. If we correct this problem, I'm pretty confident the time per loo

RE: Simple bash script is slow to execute - appears to be time spent starting commands like ls

Jeremy Bopp wrote: While I believe the usual forking performance issue is probably the largest factor for your problem, you *are* running an instance of Windows Explorer. It's displaying your desktop which as you indicate above is holding the folder containing your work area. My guess is that yo

Simple bash script is slow to execute - appears to be time spent starting commands like ls

All my bash scripts appear to run very slowly. But I have one very simple example in particular here, so I figure I'd use it to ask if there's anything I can do. This very simple script (below) takes about 2 seconds per for loop execution. That seems very high to me, based on my experience as a de