X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,KAM_TIME,KHOP_THREADED,NML_ADSP_CUSTOM_MED,RCVD_NUMERIC_HELO,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Zach Saw Subject: Re: App runs 8x slower on dual core machine (with test case to replicate issue) Date: Fri, 10 Aug 2012 04:18:46 +0000 (UTC) Lines: 19 Message-ID: References: <20120809081720 DOT GQ31757 AT calimero DOT vinschen DOT de> <50248583 DOT 30901 AT tlinx DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Zach Saw 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