Xref: utzoo comp.arch:4764 comp.databases:989 Path: utzoo!mnetor!uunet!husc6!hscfvax!pavlov From: pavlov@hscfvax.harvard.edu (G.Pavlov) Newsgroups: comp.arch,comp.databases Subject: Re: Unix machines for large databases Message-ID: <565@hscfvax.harvard.edu> Date: 11 May 88 00:42:04 GMT References: <564@hscfvax.harvard.edu> <3102@edm.UUCP> Organization: Health Sciences Computing Facility, Harvard University Lines: 14 In article <3102@edm.UUCP>, news@edm.UUCP (news software) writes: > #> I think (from the propaganda I've heard) that something like oracle > #> might sort a fit your bill. One of the ways that they do this is by use > #> of raw disk I/O rather than putting the data base into the filesytem space. > #> > # But using raw disk i/o per se doesn't guarantee anything, does it ? I think > It tends to promise that address locality implies spacial locality. This is > a nice assumption to be able to make when you want to improve your speed. > -- I did not mean that raw disk i/o can't be put to good use. But particular techniques and technologies are just that; they may make great copy in an advertising campaign, but they are no guarantee of a superior (or even good) product.