🚀 go-pugleaf

Fredrik.Pettersson@sto1.wmdata.se wrote:
> 
> Dan Pop <danpop@mail.cern.ch> wrote:
> 
> [snip]
> 
> >Is it?  Pray tell, how is MacOS multitasking the following "application":
> 
> >main() { for(;;); }
> 
> I did one of those on a NT at work and it really shared processor time nicely,
> 100% to that process and nothing to the other applications.
> 
> So if you write your applications badly they will lock system more or less even
> in a preemtive environment.
> 
>Is it my ignorance or could I be right on this point?

If this is really the case, then there is something wrong with NT. I did this
just now on this linux box, and running top showed that the "program" was using
~97% of the cpu. Hmmm, I thought...so grabbed a window and started moving it
around (I use opaque window moves, a sure CPU hog) and sure enough - the
"program" now used less than half the CPU time it used before, with the X server
now getting a nice big chunk. I started XGalaga and started dragging *that*
around, another CPU hog, and our little test program now used a rather small
chunk of CPU time.

So if your point is that bad programs can easily lock up bad systems, I'll agree
with you. But I find it hard (hard, not impossible) to believe NT can get locked
up and unresponsive _that_ easily.

I do know for a fact that it had no effect on the responsiveness of this P75
linux box.

-- 
------------------------
Damir Smitlener
damir@mindpsring.com
gt7092d@prism.gatech.edu