Gene Smith wrote:
I don't think it is a problem with cygwin itself. I was mainly
curious if anyone sees the "system" task running 50% when doing a gcc
build using Make (or similar intensive long term activity). I have
weak XP based laptop with no corporate security that runs cygwin fine
compared to my dual-core corporate desktop machine. I will check it
on the laptop but it is not with me now. Thanks for the reply.
Attached is my cygcheck.out (some private info is redacted).
I just did a compare by running the same "make" build using cygwin
(rxvt), msys (also rxvt) and cmd. With msys and cmd I see "system"
process running occasionally and for a short time at a maximum of 20%
cpu. Usually I see the "make" process or just "system idle" and the
build completes in about 22 seconds.
With cygwin/rxvt, as described previously, I see "system" process at
40-50% (usually 50%) and nothing else using cpu comes to the top. The
same build takes about 14 minutes on cygwin.
Running in the standard cygwin shell (not rxvt) the time is the same,
14 minutes compared to 22 seconds under msys/rxvt and cmd shells.
I removed the 2nd cygwin1.dll in the path that it warns about but it
made no difference.
Is there anything evident in the cygcheck that accounts for the
extreme running of the windows "system" process with cygwin active?