Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!henry
From: henry@utzoo.UUCP (Henry Spencer)
Newsgroups: net.arch
Subject: Re: Real Reasons For Large Main Memories  ( not for bozos! )
Message-ID: <7113@utzoo.UUCP>
Date: Thu, 11-Sep-86 13:51:49 EDT
Article-I.D.: utzoo.7113
Posted: Thu Sep 11 13:51:49 1986
Date-Received: Thu, 11-Sep-86 13:51:49 EDT
References: <1161@bu-cs.bu-cs.BU.EDU> <8529@duke.duke.UUCP>, <1112@tekig5.UUCP>
Organization: U of Toronto Zoology
Lines: 16

>   1. Move your file system in to memory.  ( Big bennifits.)

A potentially useful approach, but remember that most file systems contain
a modest amount of heavily-used stuff and a lot of seldom-used stuff.  It
may be better to use that memory for a big, intelligently-managed buffer
cache, which will give 90% of the speedup while using 10% of the memory.
(Or, alternatively, will give 90% of the speedup for a filesystem ten times
as large, using the same amount of memory.)

>   7. Recursion anyone?  How about recursive compilers, hmm makes me wonder.

The PDP11 cc, running in a distinctly small address space, is a recursive
design.
-- 
				Henry Spencer @ U of Toronto Zoology
				{allegra,ihnp4,decvax,pyramid}!utzoo!henry