Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <005201c15543$70c89d50$562fa4cb@co3007967a>
From: "Travis Howell" <kirben AT optushome DOT com DOT au>
To: "Cygwin Library General Discussion" <cygwin AT cygwin DOT com>
References: <3BC76CD8 DOT 7090305 AT home DOT com>
Subject: Re: More about slowing down the machine
Date: Mon, 15 Oct 2001 16:34:28 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

I noticed the exact same problem long ago now (
http://sources.redhat.com/ml/cygwin/2001-06/msg00416.html ) on Windows ME,
the worse part was the slow downs continued after all Cygwin shells were
close down (No Cygwin processes in memory according to the various Task
Manager program I tried at time). So it forces a system reboot each time it
occurrs or system becomes extremely slow the longer you let it continue.
Unfonrtunately the only options offered back then was build a debug Cygwin
or switch to Windows 2000. The first option would be hell considering how
much the system slowed down with a few simple compiles so I choose the
latter option myself.

----- Original Message -----
From: "David A. Cobb" <superbiskit AT home DOT com>
> Win98se (4.10.2222) en_US; Cygwin1.dll 1.3.4s (2001-10-11 [I think]).
>
> I was attempting another build last p.m. and, to get a handle on the
> slowdown reported in
> http://sources.redhat.com/ml/cygwin/2001-08/msg00988.html
> I ran Windows Taskinfo while it was processing.
>
> ./configure went fine [along with everything it called]
>
> As soon as MAKE started, the time anomalies began.  Watching the
> statistics with the running procedure stack:
> rxvt->WINOA386->bash->VM:->bash.2->make.1->sh.1->make.2->sh.2->gcc
> it appears that a lot of time is spent in *make.2*.  Since that process
> [I think] should simply be waiting for *sh.2* to complete, this looks
> like a spin-lock to me.
>
> To repeat, when the anomaly is happening Windows is unable to track the
> mouse and the Windows clock is being updated at about 1/4 speed.  The
> build started at 18:30 - and the clock was right - and ended at 21:00
> with the clock reading 19:05.  Somehow the message queue(s) aren't being
> checked and "pre-emptive scheduling" isn't very much so.
>
> I would like to help track this down instead of bitching all the time.
> How should I instrument this, since it's all wrapped up like an onion?
> If make builds OOTB, I suppose I could compile it with profiling.  Would
> that help?  Strace would probably show something useful - the problem
> would be to find who to trace and monkey about with the makefiles so it
> happens: bleaghh.
>
> Any wise suggestions would be greatly appreciated.
> --
> David A. Cobb, Software Engineer, Public Access Advocate, All around
> nice guy.
> New PGP key 09/13/2001:
> :<http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=superbiskit&\
> fingerprint=on>
> :<http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=superbiskit&\
> fingerprint=on>
> Fingerprint=0x{E7C6_4EE2_6B75_5BA3_C52E__77FA_63C3_9366_DCFB_229B}
> "By God's Grace I am a Christian man, by my actions a great sinner."
> --The Way of a Pilgrim, R. M. French [tr.]
> Potentially Viral Software is any software for which you are not allowed
> to examine the source.  Do not buy or use Potentially Viral Software!
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/