Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!dimacs.rutgers.edu!mips!daver!intersil!hamilton
From: hamilton@intersil.uucp
Newsgroups: comp.sys.amiga.tech
Subject: Re: Scheduler changed under 2.0?
Message-ID: <180.274171f9@intersil.uucp>
Date: 14 Nov 90 16:34:01 GMT
References: <90312.082534GIAMPAL@auvm.auvm.edu>
Organization: Harris Semiconductor, Santa Clara CA
Lines: 24

In article <90312.082534GIAMPAL@auvm.auvm.edu>, GIAMPAL@auvm.auvm.edu writes:
> I've got a semi-simple question about the Scheduler and LoadSeg() under
> 2.0 of AmigaDOS.
> 
> There seems to be a difference in the way the system handles a heavy load
> between 2.0 and 1.3 of the OS.  For example, on an A3000, if you start a ray-
> trace with TurboSilver and pop back to workbench to start up something like
> DeluxePaint, the entire system _seems_ locked, but then suddenly jumps back
> to life in little bursts.  However, under 1.3 (on the same physical machine),
> there is no noticeable delay, and DeluxePaint (or anything for that matter)
> comes up just fine with no delays or jumps in performance (i.e. things run
> smoother).  This type of performance also appears when just doing things like
> opening an icon on workbench or running other programs.

I've seen the same thing.  I was downloading a file while trying to do
something else and the system got *extremely* slow and jerky, and the 
download kept failing.  I was running some program (I can't remember which
one now) that was number crunching or rendering or otherwise using every 
free cycle, but it was running at 0 priority, so I don't know why it would
screw-up the inputdevice.
-- 
Fred Hamilton                  Any views, comments, or ideas expressed here
Harris Semiconductor           are entirely my own.  Even good ones.
Santa Clara, CA