Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!caen!sol.ctr.columbia.edu!emory!gatech!hubcap!ncrcae!ncr-sd!se-sd!cns!dltaylor
From: dltaylor@cns.SanDiego.NCR.COM (Dan Taylor)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: Peter, can you explain to the Amigoids (was: NeXT software size
Message-ID: <940@cns.SanDiego.NCR.COM>
Date: 8 May 91 01:37:50 GMT
References: <d*bGl.#*1@cs.psu.edu> <11866@uwm.edu> <*05Gx0x&1@cs.psu.edu>
Organization: NCR Corp. SE-San Diego
Lines: 17

In <*05Gx0x&1@cs.psu.edu> melling@cs.psu.edu (Michael D Mellinger) writes:

>No, they will run at the same speed, unless you get swapping but that
>will depend on how much memory you have.  Once the working set is in
>the computer, it doesn't swap until it needs a page that isn't in
>memory.

THAT is exactly the point.  While your program is still LOADING the
working set, the Amiga program is already running!.  You don't get
your first 500K into memory, through the filesystem, any faster than
we do (if as fast).  So we get a second and a half, or more, of run-time
while the OTHER 1.5 meg loads on a NeXT.  Although, if the kernel still
has the bsd-ish features I suspect, all that happens when you start a
program is the process table is fixed up, then EVERY page is paged in,
as needed.  What does THAT do to your access time for pages 2,3,4,...?

Dan Taylor