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 From: "Neal Symms" To: Subject: RE: bash backtick operator very slow Date: Thu, 31 Mar 2005 13:41:43 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: X-IsSubscribed: yes > -----Original Message----- > From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf > Of Igor Pechtchanski > > > ~$ time hostname > > MY_HOSTNAME > > real 0m0.111s > > user 0m0.060s > > sys 0m0.040s > > [...] > > > > ~$ time echo `hostname` > > MY_HOSTNAME > > real 0m6.175s > > user 0m0.060s > > sys 0m0.050s > > > > ..and that was a fast one. Usually it takes > 7 seconds. > > Does help? > Thanks; that's it exactly, Igor. I was focusing on the backtick, but it seems to have something to do with spawning shells while there is ANY low-priority process sucking up all the idle CPU. The latest cygwin1.dll snapshot solved this problem. I didn't find the answer in my searches because I was focusing on bash & backticks... Neal -- 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/