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 Date: Fri, 27 May 2005 20:50:54 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Serious performance problems (malloc related?) Message-ID: <20050528005054.GB7522@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <4297A14B DOT 9070409 AT plausible DOT org> <20050527234027 DOT GA7522 AT trixie DOT casa DOT cgf DOT cx> <4297B572 DOT 9050200 AT plausible DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4297B572.9050200@plausible.org> User-Agent: Mutt/1.5.8i On Fri, May 27, 2005 at 05:04:02PM -0700, Andy Ross wrote: >Christopher Faylor quipped: >> It seems pretty clear to me that if this is a really serious problem >> for you then the best way to get it fixed is to gain more than zero >> knowledge of cygwin. > >Gee, thanks. Very helpful. Can you at least type the commands in and >verify the problem for me before you get snippy? I said "zero >knowlege" in an attempt to be modest*, but if you really want to get >into a tussle about developer credentials, I'm happy to oblige. > >* I mean, come on: it's a 20 line program that shows a 15x performance > regression in a real-life, non-trivial application > (http://www.flightgear.org), takes all of 5 commands to verify that > can be copied right out of the source code, and even comes with a > (IMHO) pretty insightful guess as to where the problem might lie. > Most developers have erotic fantasies about this kind of bug report. Gee, I'm sorry you thought I was being "snippy". You apparently missed that I was just providing you with some obvious advice. You state that this is a "rather serious problem". It seems like if this was a really serious problem you'd be actively working towards solving it rather than sending out email and hoping to get lucky. If you think it is malloc that is causing the problem then instrumenting malloc to prove your assertion is not that much work. Building the dll is probably not five commands but it is not a heck of a lot more than that. cgf -- 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/