This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: cygwin1.dll and cygstdc++-6.dll account for over 70% of application runtime cost
- From: Mark Geisert <mark at maxrnd dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 18 Nov 2014 19:27:07 +0000 (UTC)
- Subject: Re: cygwin1.dll and cygstdc++-6.dll account for over 70% of application runtime cost
- Authentication-results: sourceware.org; auth=none
- References: <546A96B9 dot 5060507 at web dot de> <546A9B74 dot 5020807 at web dot de> <546B336E dot 6010904 at web dot de> <1DD30E94-585F-4096-BC50-24F8C2EC2AA4 at cygwin dot com>
Corinna Vinschen writes:
> On November 18, 2014 12:54:22 PM CET, Olumide wrote:
> >Thanks Corinna.
> >
> >My application does not explicitly use XSI IPC functions. It's an
> >ordinary C++ application compiled with gcc.
>
> Your app calls shmat, either the exe or some DLL.
>
> >BTW, are ZN4muto7releaseEP7_cygtls and ZN4muto7acquireEm also XSI
> >function?
>
> No, these are Cygwin-internal sync methods, apperantly called quite often
I suspect it's either the IPC functions are called quite often, or the
profiler's timer interrupts are hitting so fast relative to the speed of IPC
that you're always caught on a Windows kernel call (such as an event wait)
underlying Cygwin's IPC implementation.
Looks like the OP would have to debug the app and set a breakpoint at shmat
to determine which DLL is using IPC if the app isn't.
..mark
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple