Xref: utzoo comp.sys.misc:2013 comp.sys.pyramid:299 comp.sys.sequent:142
Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!ucbvax!agate!bionet!csd4.milw.wisc.edu!leah!bingvaxu!sunybcs!boulder!ccncsu!bizet.CS.ColoState.Edu!rro
From: rro@bizet.CS.ColoState.Edu (Rod Oldehoeft)
Newsgroups: comp.sys.misc,comp.sys.pyramid,comp.sys.sequent
Subject: Re: benchmark info.
Keywords: sequent, pyramid
Message-ID: <1024@ccncsu.ColoState.EDU>
Date: 20 Jan 89 20:56:22 GMT
References: <55653@pyramid.pyramid.com>
Sender: news@ccncsu.ColoState.EDU
Reply-To: rro@bizet.CS.ColoState.Edu.UUCP (Rod Oldehoeft)
Organization: /etc/organization
Lines: 13

In article <55653@pyramid.pyramid.com> bejc@pyrnova.UUCP (Brian Clark) writes:
>In article <55614@pyramid.pyramid.com> csg@pyramid.pyramid.com (Carl S. Gutekunst) writes:
>>
>>When I buy machines, I try establish a matrix of priorities versus machines,
>>and mark down which machines will meet each priority. This is a big help in
>>eliminating emotional biases. Of course, whether or not the applications you
>>need run on that particularly machine should be very high on the matrix. 
>>
>Quite independently of Carl I have developed a similar way of system based
>around a matrix of priorities, I can email or smail a sample to anyone who's
>interested. 
>
How about a posting?