carlos@pooh.caltech.edu (07/15/90)
I don't want to start a religious discussion, but... From what I've read about Unix's scheduling algorithm, CPU intensive activities are scheduled with a low priority, I/O intensive activities are scheduled with a higher priority. Why? To increase the responsiveness of a terminal login (I/O intensive.) So whenever you do I/O intensive stuff like file phun and the Window Server (CPU intensive) slows down, blame Unix not NeXT. Funny how one of the few "standards" that slipped into the system is one of its greatest drawbacks. BTW- Notice how NeXT avoids using Unix in most apps? Luckily NeXT is not entirely Unix, the core system is Mach. This leaves the door open for better schedulers. Carlos Salinas carlos@eeyore.caltech.edu <- NeXT mail