Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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: Sat, 28 May 2005 13:24:31 +0200 (CEST)
From: Vaclav Haisman <V DOT Haisman AT sh DOT cvut DOT cz>
Cc: cygwin AT cygwin DOT com
Subject: Re: Serious performance problems (malloc related?)
In-Reply-To: <4297A14B.9070409@plausible.org>
Message-ID: <20050528131501.V53507@logout.sh.cvut.cz>
References: <4297A14B DOT 9070409 AT plausible DOT org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com


I have similar problem with CPU bound program of mine on Cygwin too. The
difference is something like 35 minutes versus 400 seconds on the same machine
but under FreeBSD.

Somebody mentioned that malloc implementation could be the problem. Dunno. I
has also crossed my mind that another difference between FreeBSD and Cygwin is
implementation of C++ exceptions. Maybe the SJLJ implementation that Cygwin
AFAIK uses has too big overhead.

VH

PS: I think that cgf should really try to improve his PR skills.

--
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/