Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!gatech!psuvax1!julius.cs.uiuc.edu!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!lobster!nuchat!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.advocacy Subject: Re: How do we change the scheduler? (Was Re: Multitasking at home...) Message-ID: <7589@sugar.hackercorp.com> Date: 23 Jan 91 13:40:41 GMT References: <1991Jan18.231330.16290@Neon.Stanford.EDU> <7553@sugar.hackercorp.com> <1991Jan21.004720.25985@ncsuvx.ncsu.edu> <12880@life.ai.mit.edu> <1991Jan21.055854.14130@rice.edu> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Distribution: usa Organization: Sugar Land Unix - Houston Lines: 13 In article <1991Jan21.055854.14130@rice.edu> jsd@wahoo.rice.edu (Shawn Joel Dube) writes: > Two task are running. One is waiting on a keypress (via OS subroutine) > and the other is doing some serious number-crunching. With the Amiga, valuable > time is being spent doing nothing (waiting for a keypress). With co-op > multitasking, almost all of the cpu time is spent with the number cruncher. I think you have things backwards. On the Amiga a task waiting for a keypress takes up zero CPU time. Not "almost no" CPU time, Zero. It's not even on the ready queue. It's in a wait state. On the Mac a program waiting for a keypress has to sit there and handle all the events coming into it from WaitNextEvent. -- Peter da Silva. `-_-' .