Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rochester!sher
From: sher@rochester.ARPA (David Sher)
Newsgroups: comp.arch
Subject: Re: 64 Vs 32
Message-ID: <26084@rochester.ARPA>
Date: Wed, 18-Mar-87 16:57:20 EST
Article-I.D.: rocheste.26084
Posted: Wed Mar 18 16:57:20 1987
Date-Received: Fri, 20-Mar-87 01:40:53 EST
References: <3810013@nucsrl.UUCP> <985@rpics.RPI.EDU> <1310@ucbcad.berkeley.edu> <508@cpocd2.UUCP>
Reply-To: sher@rochester.UUCP (David Sher)
Organization: U of Rochester, CS Dept, Rochester, NY
Lines: 11
Keywords: gigabyte memory usage image processing
Summary: Lots of extra memory allows more table lookup

Remember that any kind of calculation can be speeded up and made more
accurate by using table lookup.  Thus instead of using cumbersome and
slow calculations to do sin just do table lookup.  (You'd be surprized
how many applications could use a fast sin function).  The more memory
the more functions can be economically made into tables.  Thus one can
justify larger memory for any user who has critical functions that are slower
than a few memory references.
-- 
-David Sher
sher@rochester
{allegra,seismo}!rochester!sher