On Wed, 9 Apr 2008, Peter O'Gorman wrote:
(using bash) $ for y in {1..100}; do echo "func_notused${y} () {" >> parse.sh; for x in {1..10000}; do echo foo >> parse.sh; done; echo '}' >> parse.sh; done; echo 'echo Done' >> parse.sh
It seems that the slowest possible shell is selected by default. Maybe that is bad?
On Solaris 10 (Opteron) % ptime bash parse.sh Done real 3.247 user 2.923 sys 0.322 % ptime zsh parse.sh Done real 0.991 user 0.877 sys 0.112 % ptime ksh parse.sh Done real 1.063 user 0.922 sys 0.141 On Solaris 10 (SPARC) % ptime bash parse.sh Done real 10.417 user 10.128 sys 0.283 % ptime zsh parse.sh Done real 3.045 user 2.817 sys 0.227 % ptime ksh parse.sh Done real 3.432 user 3.255 sys 0.175 On FreeBSD 7.0 (Intel Xeon) % time bash parse.sh Done bash parse.sh 5.63s user 0.18s system 99% cpu 5.808 total % time zsh parse.sh Done zsh parse.sh 2.02s user 0.36s system 99% cpu 2.379 total On Mac OS-X Leopard (G5) % time bash parse.sh Done bash parse.sh 4.46s user 0.41s system 99% cpu 4.891 total % time zsh parse.sh Done zsh parse.sh 1.35s user 0.39s system 83% cpu 2.074 total % time ksh parse.sh [ runs forever apparently ] ====================================== Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool