Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!wuarchive!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!dsac.dla.mil!dsacg3.dsac.dla.mil!desc.dla.mil!wright!desire.wright.edu!cse0735
From: cse0735@desire.wright.edu
Newsgroups: comp.sys.mac.system
Subject: Re: Virtual Memory and Sys 7
Message-ID: <1991May14.211319.3604@desire.wright.edu>
Date: 15 May 91 02:13:19 GMT
References: <1991May8.143042.20137@bigsur.uucp>
Organization: University Computing Services, Wright State University
Lines: 24

In article <1991May8.143042.20137@bigsur.uucp>, webster@bnr.ca (Brent Webster) writes:
> 
>   Is Apple's version of virtual memory always going to be
>   HARDDISK hungry?
> 
>   Or is this all fixed in the official "May 13" release of 
>   System 7?

I suspect that it was a trade off for speed since Apple couldn't assume that
everyone was going to have a super fast backing store. By doing a direct 1:1
map of the virtual memory to disk space, tey didn't have to go through extra
logic to locate where pages of memory were stored on the disk. And when you
are running on a machine that doesn't have an I/O coprocessor for hard disk
access, and the possibility of slow drives, I think they could use every iota
of speed they could squeeze out of thier memory swapper.
 
(***********************************)
(*    Chris Blouch                 *)
(*    Wright State University      *)
(*    Dayton, Ohio                 *)
(*                                 *)
(***********************************)