X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <47FA8298.121F0D3D@dessent.net> Date: Mon, 07 Apr 2008 13:22:48 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Performance question References: <47FA2338 DOT 7060202 AT w1hkj DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com 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 w1hkj wrote: > There is is very significant difference in cpu usage between running the > application from the Cygwin X-terminal and running from the run command > (with the cygwin1.dll) from Windows. > > System X-term Windows-Run > HP Athalon 33% 100% > Dell 3000 3 % 55% How much text/console output is involved in this testcase? I find that when run from a Windows Console, any significant amount of stdout is much slower than when using rxvt/xterm. I think it's partly because the Windows Console is just a lot slower, but also because I have Lucida Console, a Truetype font, configured for the Windows Console (as well as Cleartype subpixel rendering enabled) which is very slow to render compared to a fixed size bitmap font that I have configured for rxvt/xterm. Brian -- 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/