Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Subject: RE: pthreads works, sorta Date: Wed, 27 Jun 2001 14:46:10 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-ID: content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: pthreads works, sorta Thread-Index: AcD+wg2cO46JKZKQR2K/Y/OUKKrAwgAAGc9w From: "Robert Collins" To: "Greg Smith" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id AAA29295 > -----Original Message----- > From: Greg Smith [mailto:gsmith AT nc DOT rr DOT com] > > Ummm, no ;-) Performance is now on pretty even keel with > with the Pthread-win32 implementation. This is where our > `rogue' developer (`Fish') is claiming to reduce elapsed times > 25% to match the elapsed times on linux. Is your app cpu bound/sync or contention bound/ or io bound? (for that 25% ?) Also other cygwin internals use VirtualQuery. I'm going to look into all instances of VirtualQuery :] As pthread-win32 is coded by some pretty clued up folk, (and we've met their speed :} ) I wouldn't hold much hope of shaving more time off from pthreads. CriticalSections may help. Profiling your app is probably essential. (to understand where in cygwin/pthreads things need tuning). Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/