Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authenticated: #21620914 Message-ID: <004701c56f79$1eb791c0$d119fea9@pcdahl4201> From: "Thorsten Dahlheimer" To: References: <20050610150729 DOT GA13181 AT trixie DOT casa DOT cgf DOT cx> <20050610231343 DOT 6A12713C0A7 AT cgf DOT cx> <20050611003817 DOT GB1106 AT trixie DOT casa DOT cgf DOT cx> Subject: Re: Making /bin/sh == bash. Has the time come? Date: Sun, 12 Jun 2005 20:03:41 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-IsSubscribed: yes Krzysztof Duleba wrote: > Christopher Faylor wrote: > > On Fri, Jun 10, 2005 at 06:13:31PM -0500, Gary R. Van Sickle wrote: > > >Configuring wxWindows from cvs, on a 3.4GHz P4: > > > > > >Sh = Ash: > > >real 3m55.351s > > >user 5m8.610s > > >sys 1m53.240s > > > > > >Sh = Bash: > > >real 3m41.850s > > >user 5m6.220s > > >sys 1m53.426s > > > > > >Looks like the time has come. > > > > Wow. I never expected that bash would actually be faster. > > > > I would appreciate getting a few more benchmarks for other packages. > > If this holds out then moving to bash is a no-brainer. > > Similar results here. Configuring on Athlon 2200 gives > > 1. octave 2.1.57: > sh = ash > real 2m48.347s > user 4m13.299s > sys 1m25.203s > > sh = bash > real 2m38.129s > user 4m11.777s > sys 1m23.915s > > 2. netcat 0.7.1 > sh = ash > real 0m56.847s > user 1m29.808s > sys 0m30.186s > > sh = bash > real 0m57.015s > user 1m28.878s > sys 0m29.338s > > 3. mc 4.6.1-pre4 > sh = ash > real 2m13.248s > user 3m31.685s > sys 1m9.772s > > sh = bash > real 2m10.112s > user 3m30.198s > sys 1m10.563s Are you sure you didn't actually measure bash's performance twice? If you simply run configure with ash, it will effectively do an exec /bin/bash "$0" "$@" at the beginning, unless you force it to stick with ash by setting CONFIG_SHELL=/bin/sh. FWIW, I did find that the configure scripts I tested ran faster under ash than under bash, but only by 4% to 8%. Regards Thorsten Dahlheimer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/