Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ll-xn!cit-vax!news
From: news@cit-vax.Caltech.Edu (Usenet netnews)
Newsgroups: comp.arch
Subject: Re: 64 Vs 32
Message-ID: <2050@cit-vax.Caltech.Edu>
Date: Mon, 16-Mar-87 18:06:36 EST
Article-I.D.: cit-vax.2050
Posted: Mon Mar 16 18:06:36 1987
Date-Received: Tue, 17-Mar-87 04:26:36 EST
References: <3810013@nucsrl.UUCP> <985@rpics.RPI.EDU> <1310@ucbcad.berkeley.edu>
Reply-To: jon@oddhack.UUCP (Jon Leech)
Organization: California Institute of Technology
Lines: 21

Organization : California Institute of Technology
Keywords: 
From: jon@oddhack.Caltech.Edu (Jon Leech)
Path: oddhack!jon

In article <1310@ucbcad.berkeley.edu> faustus@ucbcad.berkeley.edu (Wayne A. Christopher) writes:
>What we need to ask is, who will need more than ~1G of memory?  I think
>the only applications that currently could use this much memory are
>scientific programs that run on Crays (which I think are addressible to
>the 64-bit word anyway).  I certainly haven't been running into the 1G
>limit too often lately.

	People doing graphics. One of the people here has ray-traced
a picture containg 4e11 polygons. The only way he could get away with
it right now is by having multiple levels of instantiation of objects,
resulting in a very boring scene, but eventually we will want that many
DIFFERENT objects. There will never be enough memory.

    -- Jon Leech (jon@csvax.caltech.edu || ...seismo!cit-vax!jon)
    Caltech Computer Science Graphics Group
    __@/