From: Zach Saw <zach.saw@gmail.com>
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 06:31:00 -0000 [thread overview]
Message-ID: <loom.20120810T061532-598@post.gmane.org> (raw)
In-Reply-To: <loom.20120810T060448-506@post.gmane.org>
Zach Saw <zach.saw <at> gmail.com> writes:
> > On Cygwin:
> > This is perl 5, version 14, subversion 2 (v5.14.2) built for
> > cygwin-thread-multi-64int
>
> Just out of curiousity are you running XP-32bit?
> If you are, could you try running the multithreaded test with CPU
> affinity set to 1 (single core)?
> You should see it take just a little more time to complete vs the
> single threaded one.
Actually, you'd be running under 64-bit Windows with perl being
compiled as native 64-bit app. In which case, could you also try
what I described above?
You should be able to set CPU affinity of the perl process by first
setting affinity of a parent process (e.g. cmd.exe). Then run perl
from that cmd.exe. Child processes will follow the affinity.
--
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
next prev parent reply other threads:[~2012-08-10 4:19 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
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 [this message]
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=loom.20120810T061532-598@post.gmane.org \
--to=zach.saw@gmail.com \
--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).