From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Machine very sluggish while compiling
Date: Fri, 25 Nov 2011 04:07:00 -0000 [thread overview]
Message-ID: <4ECEE88E.5050307@cs.utoronto.ca> (raw)
Hi all,
Lately I've noticed that running make -j4 on my quad-core win7-x64
machine causes it to become sluggish or even unresponsive. For example,
compiling a large package makes the mouse jumpy, delays keystrokes, adds
stutter to my music, and makes task switching painfully slow (though,
oddly, if I manage to switch to the mintty that runs make the machine
"comes back"). The sluggishness always hits when I'm using a native
windows app with the compile running in the background. This starts to
sound oddly like the recently-reported issue where X was causing native
windows apps to freeze [1].
I'm not seeing any fork failures, and am running BLODA-free (Windows
Defender hasn't reappeared since I last uninstalled it). There's no
unusual disk activity and memory utilization remains stable. I've tried
running with nice, reducing the priority of 'make' from the task
manager, and running make -j3 to no avail, though empirically if
utilization stays at or below 2 cpu then there's no problem. I've
compiled large apps (gcc, binutils, emacs, gdb, ...) off and on for
several years now and never seen this behavior before.
Any ideas of how I might diagnose the issue further? It's easy enough to
work around, but compiles take a lot longer with only 1-2 cores instead
of 4.
Thanks,
Ryan
[1] http://cygwin.com/ml/cygwin-xfree/2011-11/msg00027.html
--
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 reply other threads:[~2011-11-25 1:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 4:07 Ryan Johnson [this message]
2011-11-25 4:17 ` Mike
2011-11-25 7:22 ` Ryan Johnson
2011-11-25 15:48 ` Spiro Trikaliotis
2011-12-04 7:55 ` Ryan Johnson
2011-12-04 10:07 ` Corinna Vinschen
2011-12-05 22:25 ` Ken Brown
2011-12-06 10:39 ` Corinna Vinschen
2011-12-08 11:18 ` Robert Miles
2011-12-08 13:15 ` Ryan Johnson
2011-12-04 19:29 ` Christopher Faylor
[not found] ` <4EDBD5A5.2000707@cs.utoronto.ca>
2011-12-04 20:23 ` Ryan Johnson
2011-12-06 17:39 ` Andrew Schulman
2011-12-07 5:23 ` Mike
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=4ECEE88E.5050307@cs.utoronto.ca \
--to=ryan.johnson@cs.utoronto.ca \
--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).