[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MiNT scheduling



On Wed, 12 Nov 1997, Konrad Kokoszkiewicz wrote:

> > I have observed that when a process is running under MiNT that requires a
> > lot of processor time, for example raytracing, response to keypresses and
> > mouse clicks seems to slow down significantly.
> 
> Yes, I noticed the same thing on Falcon. I tried to run gcc in the
> background and, while compiling something, I tried to write a text in QED.
> But the keyboard response was too slow and any serious work in a GEM text
> editor was impossible.

I have an Afterburner, and I can safely say that neither MiNT alone
nor MiNT/N.AES is slow ;-) True, things can slow down during
compiling, but that's due to the heavy diskaccess. Background DMA is
unfortunelately impossible under MiNT, so I'm afraid we'll have to
live with this...

With other CPU-intensive tasks that doesn't access the disk much (like
raytracing or compressing large archives) I don't notice any slowdown
with N.AES. But again, this is on an Afterburner. I can't remember
that I had any problems before I got the AB though.

> Actually QED's key response is too slow even without gcc running, just the
> usuall MiNTOS stuff makes the computer slow. There's no such problem in 
> normal MultiTOS setup (i.e. an AES without MiNTOS). I have no idea how to
> solve it.

...and I don't have a clue. I've been using the KGMD/N.AES-combination
for almost a year now, the first seven months I used it on a 14Mb
18MHz Falcon without problems. QED has always worked perfectly here,
regardless of environment.


/*
** Jo Even Skarstein    http://www.stud.ntnu.no/~josk/
**
**    beer - maria mckee - atari falcon - babylon 5
*/