Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!ernie.Berkeley.EDU!jas
From: jas@ernie.Berkeley.EDU (Jim Shankland)
Newsgroups: comp.databases
Subject: Re: Ingres Phasing Out at Berkeley
Message-ID: <29296@ucbvax.BERKELEY.EDU>
Date: 24 May 89 01:20:06 GMT
References: <24519@agate.BERKELEY.EDU> <3560039@wdl1.UUCP> <24756@agate.BERKELEY.EDU>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: jas@ernie.Berkeley.EDU.UUCP (Jim Shankland)
Organization: University of California, Berkeley
Lines: 27

In article <24756@agate.BERKELEY.EDU> steve@violet.berkeley.edu (Steve Goldfield) writes:
>[My group was the principal one using, and paying for, INGRES on VAXen;
>we've decided to move to a cheaper departmental computer, so the University
>will no longer purchase INGRES for the VAXen.]
>Still, I find it ironic that here in Berkeley,
>where Ingres was born, it doesn't get much respect.
>
Your conclusion (INGRES doesn't get much respect) doesn't follow from
the circumstances you describe.  It hasn't been my experience here at
Berkeley.

>in a corporate environment ... exorbitant charges for cpu time are not
>as relevant as they are for us in which we pay, in cash, for our usage.
>As long as your equipment is powerful enough not to be brought to
>its knees by Ingres and as long as Ingres does its job,
>presumably you are relatively satisfied.

Relational database systems have always been great resource hogs.
Near as I can tell, they're all gradually getting better.  More important,
the days of "exorbitant charges for cpu time" are numbered (unless your
need for cpu time runs into the several hundreds of MIPS).  I guess we'll
still be contending with each other for I/O bandwidth ....

Jim Shankland
jas@ernie.berkeley.edu

"Blame it on the lies that killed us, blame it on the truth that ran us down"