public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: cygwin@cygwin.com
Subject: Re: App runs 8x slower on dual core machine (with test case to replicate issue)
Date: Fri, 10 Aug 2012 03:45:00 -0000	[thread overview]
Message-ID: <5024835E.1070102@dancol.org> (raw)
In-Reply-To: <loom.20120810T052639-721@post.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 912 bytes --]

On 8/9/12 8:29 PM, Zach Saw wrote:
> Corinna Vinschen <corinna-cygwin <at> cygwin.com> writes:
> 
>> Thanks for the testcase, but... would you mind to change it to take the
>> boost lib out of the picture, by using just plain pthread functions, if
>> possible in plain C?
> 
> Apparently someone else has already encountered similar problems in 
> cygwin perl 
> (http://www.nntp.perl.org/group/perl.perl5.porters/2011/07/msg174491.html)
> last year that went unfixed. Now that you have a test case in C++/Boost, 
> you're asking for plain pthread/C?

Cygwin developers are experts in Cygwin, not Perl or Boost. Their job
is hard enough as it is. If you're not interested in being helpful,
I'm sure someone will sell you a support contract.

I don't know what Boost's threadpool uses internally, but if you
consult the source, you should be able to come up with a good testcase
in plain C.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 235 bytes --]

  reply	other threads:[~2012-08-10  3:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09  8:17 Zach Saw
2012-08-09  9:22 ` Corinna Vinschen
2012-08-10  3:39   ` Zach Saw
2012-08-10  3:45     ` Daniel Colascione [this message]
2012-08-10  4:04       ` Zach Saw
2012-08-10 16:37         ` Andrew DeFaria
2012-08-11  1:14           ` Zach Saw
2012-08-11  2:32             ` Christopher Faylor
2012-08-10  3:52     ` Larry Hall (Cygwin)
2012-08-10  4:10       ` Zach Saw
2012-08-10  3:56     ` Linda Walsh
2012-08-10  4:13       ` Zach Saw
2012-08-10  6:31         ` Zach Saw
2013-01-22  4:51 ` Zach Saw
2013-01-22  8:51   ` Corinna Vinschen
2012-08-09 13:03 Zach Saw

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=5024835E.1070102@dancol.org \
    --to=dancol@dancol.org \
    --cc=cygwin@cygwin.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).