This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Serious performance problems (malloc related?)
On Sat, May 28, 2005 at 10:51:01PM +0200, Vaclav Haisman wrote:
>On Sat, 28 May 2005, Gerrit P. Haase wrote:
>
>> Andy Ross wrote:
>> > But as I noted in my original post: It's not waiting on the disk
>> > reads. Comment out the split() call and watch the delays disappear.
>> > Raw I/O speed in cygwin is comparable to mingw or MSVC. The overhead
>> > is due, somehow, to activity within/under split(). Other than
>> > allocation, that function doesn't do any meaningful library
>> > interaction that I can see (although Vaclav's suggestion about
>> > exception handling is a very good one...).
>>
>> Can you port the testcase you provided to C to see if it makes a
>> difference, please?
>
>Or maybe at least try -fno-exceptions...
I tried every variation of g++ exception switches that I could think of.
It didn't make a difference.
On further investigation, it sounds like the exception stuff is a red
herring. It seems to have something to do with the fact that cygwin
uses pthread_* and, apparently, pthread* is slow. It may be that cygwin
calls in general are slow...
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/