Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Sat, 28 May 2005 13:24:31 +0200 (CEST)
From: Vaclav Haisman <V.Haisman@sh.cvut.cz>
Cc: cygwin@cygwin.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.9070409@plausible.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-IsSubscribed: yes
Reply-To: cygwin@cygwin.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/

