Just found a better solution:
you can give cygwin a lower priority.
Write a new batch file, for exampe "cygstart.bat" with the following
content:
# cygstart.bat
start "Cygwin" /low C:\cygwin\Cygwin.bat
While I'm writing this email, my tests are running :)
-----Message d'origine-----
From: Frédéric THOMAS
Sent: Sunday, October 28, 2012 1:36 PM
To: flex-dev@incubator.apache.org
Subject: Re: mustella performance
As a hint, I set the process priority of my shell lower than normal and can
use windows almost normaly while the tests are running.
-----Message d'origine-----
From: Michael Schmalle
Sent: Thursday, October 25, 2012 11:38 AM
To: flex-dev@incubator.apache.org
Subject: mustella performance
Hi,
What is going on with the mustella test suite that would make all quad
core cpus run at 100%?
I know these tests are broad but, my computer got really unstable
trying to run -all.
Fact is I don't have time to wait an hour to see if I broke something
when I am just doing edits in build files.
BTW I had to kill all the java processes to get my computer not to crash.
I'm running an HP Core Quad Q9300 2.5, 8GB Ram
I have had this computer for a couple years and never had a problem
like this only with some older programs.
Mike
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
