From: Erik Hensema <erik.hensema@group2000.nl>
To: 'Pthreads-win32' <pthreads-win32@sourceware.cygnus.com>
Subject: Performance
Date: Wed, 22 Sep 1999 07:31:00 -0000 [thread overview]
Message-ID: <A01E735D4940D311A3850090275559330BA959@NTSRV02> (raw)
Sorry if this question has been asked before on this list, but the archives
seem te be offline.
I'm preparing to port a 110 kloc application from Unix to NT. It's very
performance critical, so we don't want to use API's like Nutcracker or
Cygwin.
The application extensively uses multithreading, and we want to maximise the
performance. How does the pthread-win32 performance compare to the regular
win32 threads? And, if we aren't going to use pthreads-win32, how much
effort would it take to port our pthreads application to win32?
Erik Hensema, erik.hensema@group2000.nl
next reply other threads:[~1999-09-22 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-22 7:31 Erik Hensema [this message]
1999-09-22 16:17 ` [pthread-win32] Performance Tristan Savatier
1999-09-22 7:46 Performance Bossom, John
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A01E735D4940D311A3850090275559330BA959@NTSRV02 \
--to=erik.hensema@group2000.nl \
--cc=pthreads-win32@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).