On 1/6/11 8:17 PM, Alexander Tiurin wrote:
> Hi!
>
> I ran the command
>
> ~$ time for i in `seq 0 10000` ; do echo /o/23/4 | cut -d'/' -f2 ; done
>> /dev/null
>
> 6 times in a row, and noticed to the increase in execution time:
>
[...]
>
> how to interpret the results?
It's hard to say without doing more investigation, but I suspect that the
fork time is increasing because the bash binary is growing in size.
I'd have to build a version with profiling enabled to tell for sure.
Since Jan brought it up, I took a release candidate for bash-4.2, dropped
the DEBUG and MALLOC_DEBUG options, and ran those commands in a script
with it. Results were consistent each run: around 9-10 seconds. This
isn't great, but it didn't exhibit the pathological degradation you saw.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
