Xref: utzoo comp.arch:4711 comp.databases:981
Path: utzoo!mnetor!uunet!ncc!alberta!access!edm!news
From: news@edm.UUCP (news software)
Newsgroups: comp.arch,comp.databases
Subject: Re: Unix machines for large databases
Message-ID: <3102@edm.UUCP>
Date: 9 May 88 04:47:18 GMT
References: <564@hscfvax.harvard.edu>
Organization: Unexsys Systems, Edmonton,AB.
Lines: 15

From article <564@hscfvax.harvard.edu>, by pavlov@hscfvax.harvard.edu (G.Pavlov):
# In article <3091@edm.UUCP>, steve@edm.UUCP (Stephen Samuel) writes:
#> From article <428@cmx.npac.syr.edu>, by billo@cmx.npac.syr.edu (Bill O):
#> 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.
-- 
-------------
 Stephen Samuel 
  {ihnp4,ubc-vision,vax135}!alberta!edm!steve
  or userzxcv@uqv-mts.bitnet