X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=iV7jc9Spk3LyoqnyFrq6UFehJ3+CmuHgaHn2Yf+5tJRLAYBrREUyh KoFduqdbmzf8nukQPQwPAufAHA09HxGipa/xt+4cJobacPKIQU2DgkfQsYZk0Nf7 j0pti28rG+L9cSIN9cyrHItwRJXVUo9YoJQToklM3g908RsEy47nB0= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; s=default; bh=dXjzo23RBAP1Qu+3pZImpJBc8BI=; b=YE6jO/j8GIzYYF7KuG9RikPQgnl9 2tgqMQE5uDgNKw04/dtWlrx6Vp1EQdYo262V/U0at8y2bSga3O96Ye5XGaqo51DJ IG1MXdq2ga8Dhl3rWeBSLGqM2QmtrkXOkisGl5gpWFvXXgipjC9YITWp+4qemBKR 1d3keoh+K5SKOAg= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_40,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: plane.gmane.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: Fish Shell Speed? Date: Wed, 27 May 2015 10:09:05 -0400 Lines: 24 Message-ID: References: <5565CC40 DOT 7020100 AT tlinx DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes > David Frascone wrote: > > 1) Has anyone seen this behavior before? If so, do you remember which > > functions may be causing it (hg vs git speed under cygwin maybe?) > > > > 2) Any thoughts on trying to profile a prompt and/or shell script, if > > I pull it out of the prompt function > > Anytime you have to call an external process, you pay a multiplied > penalty on cygwin -- 1st linux process spawning, while costly, are > less than Windows, and 2) cygwin has to emulate the posix semantics > on windows -- to which it is not friendly. If you could somehow cache > recent data in data struct and only updated ever 10 minutes with a > live call, that might help...? Yeah. If you look in the standard fish_prompt function, it does some of that - cacheing calculated outputs that can be expected not to change for the duration of a single shell. My prompt isn't as bad as yours, but there's a noticeable lag in Cygwin that's not there in Linux. Profiling would be a good idea, but I don't know how you do that with a fish script. I suggest asking on the fish-users list. Good luck, Andrew -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple