>I'm not sure how deep you want to go into this project but there is
>another (fairly advanced) option with raw i/o.  In a nutshell, this
>bypasses the kernel buffer cache and gives you direct access to disk.  It
>is often used (and even required) by high-end database products.

Were I to implement this kind of thing, how badly off would this put me for
portability? The plan for this project is to get it running on a Linux box,
and when it is stable enough start running it with 2Gb + data sets on a cluster of 
sparcs (Down at Technology Park).

My plan is also to have the blocks in the database set to exactly one page
in size, which may save me some hassle(?).

Thanks

Stephen Graham
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text

Reply via email to