Article View: net.arch
Article #2730Re: Reasons For Large Main Memories
From: Scot E. Wilcoxon
Date: Mon, 01 Sep 1986 23:18
Date: Mon, 01 Sep 1986 23:18
20 lines
1674 bytes
1674 bytes
Since most net.arch readers probably don't usually read Business Week
(I was reading it for tax change info :-) I'll point out "Giving Computers
an Elephant's Memory" in BW, Sept 1 86, pg 50. Mostly about Princeton's M3
(Massive Memory Machine), but also mentions some applications for it and
several companies working on huge memories.
As a mostly-application programmer, I'm deferring comments on the present
pagefaults-and-other-problems discussion to those more knowledgeable.
As a system administrator and sometimes OS tinkerer, I expect a machine
with huge memories will let it be tuned through OS parameters (we're
currently replacing three machines partially because SCO didn't give
us a way to configure XENIX* on them).
* XENIX is a trademark of Microsoft Corporation. Nobody else wanted it.
--
Scot E. Wilcoxon Minn Ed Comp Corp {quest,dicome,meccts}!mecc!sewilco
45 03 N 93 08 W (612)481-3507 {{caip!meccts},ihnp4,philabs}!mecc!sewilco
Laws are society's common sense, recorded for the stupid.
The alert question everything anyway.
Technical Details
Message-ID:
<563@mecc.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!mnetor!seismo!caip!meccts!mecc!sewilcoReferences:
<8494@duke.duke.UUCP> <147@eneevax.UUCP>Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: arc1-ca.pugleaf.net!utzoo!mnetor!seismo!caip!meccts!mecc!sewilco From: sewilco@mecc.UUCP (Scot E. Wilcoxon) Newsgroups: net.arch Subject: Re: Reasons For Large Main Memories Message-ID: <563@mecc.UUCP> Date: Mon, 1-Sep-86 19:18:36 EDT Article-I.D.: mecc.563 Posted: Mon Sep 1 19:18:36 1986 Date-Received: Tue, 2-Sep-86 04:06:53 EDT References: <8494@duke.duke.UUCP> <147@eneevax.UUCP> Reply-To: sewilco@mecc.UUCP (Scot E. Wilcoxon) Distribution: na Organization: MN Ed Comp Corp, St Paul, MN Lines: 20 Summary: BusinessWeek 86/9/1 pg 50.