X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: From: Mike Marchywka To: Subject: RE: Updated: cygwin-1.5.25-5 Date: Mon, 10 Dec 2007 09:15:46 -0500 In-Reply-To: <20071210140334.GD6618@calimero.vinschen.de> References: <475C2AAE DOT 9030800 AT alum DOT mit DOT edu> <20071210095725 DOT GA13109 AT calimero DOT vinschen DOT de> <20071210132802 DOT GA15065 AT calimero DOT vinschen DOT de> <20071210140334 DOT GD6618 AT calimero DOT vinschen DOT de> Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id lBAEGBbJ007469 > I don't understand what you mean. Using> on the command line or > opening the file by using some option of the tool has both nothing to do > with console output. In both cases a file is opened. The only I didn't give it a lot of additional thought, I just stopped using ">" ( when I have significant amounts of output ) a while ago and assumed it had something to do with buffering- I have no idea what is going on once I call "<<" and I never did a version by version test. Similarly, I essentially stopped using std::string since for most of what I did it was easier to do a block read anyway. I'm simply pointing out that the details appear to matter and, as you request, a test case would help but the gprof output could point to some surprising suspects. Mike Marchywka 586 Saint James Walk Marietta GA 30067-7165 404-788-1216 (C)<- leave message 989-348-4796 (P)<- emergency only marchywka AT hotmail DOT com Note: Hotmail is blocking my mom's entire ISP claiming it is to reduce spam but probably to force users to use hotmail. Please DON'T assume I am ignoring you and try me on marchywka AT yahoo DOT com if no reply here. Thanks. > Date: Mon, 10 Dec 2007 15:03:34 +0100 > From: corinna-cygwin AT cygwin DOT com > To: cygwin AT cygwin DOT com > Subject: Re: Updated: cygwin-1.5.25-5 > > On Dec 10 08:40, Mike Marchywka wrote: >>> I can't reproduce worse I/O performance. I tested different scenarios >>> with lots of disc I/O and the performance was identical between 1.5.24 >>> and 1.5.25 within the bounds of a performance test. >>> >> >> >> One thing I found out, after originally blaming my inner computational loops, >> was that console IO is very slow. Using ">" on the command line makes a big >> difference compared to opening a destination file. This seemed to be the >> speed limit in many programs I thought were computationally limited. >> [...] >> Has the console buffering >> changed lately? > > I don't understand what you mean. Using> on the command line or > opening the file by using some option of the tool has both nothing to do > with console output. In both cases a file is opened. The only > difference in that in the> case the shell opens the file and the child > inherits the file descriptor, in the other case the child opens the file > by itself. However, I don't see how getting a file descriptor to a file > from the parent should be different than opening the file in the child, > at least as long as parent and child are both Cygwin processes. > > In fact, one of my tests was a loop using `cat < foo> bar', which got > much faster under 1.5.25 due to the new 64K buffering. > > Give me a really simple testcase which shows reproducibly worse > performance on 1.5.25 compared to 1.5.24 and I'll have another look. > > > Corinna > > -- > Corinna Vinschen Please, send mails regarding Cygwin to > Cygwin Project Co-Leader cygwin AT cygwin DOT com > Red Hat > > -- > 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/ > _________________________________________________________________ Connect and share in new ways with Windows Live. http://www.windowslive.com/connect.html?ocid=TXT_TAGLM_Wave2_newways_112007 -- 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/