Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!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: <7591@sugar.hackercorp.com> Date: 23 Jan 91 13:45:41 GMT References: <1991Jan18.231330.16290@Neon.Stanford.EDU> <7553@sugar.hackercorp.com> <1991Jan21.004720.25985@ncsuvx.ncsu.edu> <12880@life.ai.mit.edu> <42852@ut-emx.uucp> <1991Jan21.073234.23885@Neon.Stanford.EDU> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 15 In article <1991Jan21.073234.23885@Neon.Stanford.EDU> torrie@cs.stanford.edu (Evan J Torrie) writes: > With a preemptive multitasking system, you would still have the same > problem on a heavily loaded system. The screen saver would run to the > end of its timeslice, then the other programs would run to the end of > their timeslices, and you'd still get that pause in the animation > while the other programs are running. Not at all, that's what priorities are all about. The Amiga doesn't use a strict round-robin scheduler. I hope your screen saver uses delays after each screen instead of chucking out displays as fast as it can. What does it do on a faster CPU? -- Peter da Silva. `-_-' .