up vote 0 down vote favorite
share [g+] share [fb]

I want to ensure I have done all I can to configure a system's disks for serious database use. The three areas I know of (any others?) to be concerned about are:

  1. I/O size: the database engine and disk's native size should either match, or the database's native I/O size should be a multiple of the disk's native I/O size.
  2. Disks that are capable of Direct Memory Access (eg. IDE) should be configured for it.
  3. When a disk says it has written data persistently, it must be so! No keeping it in cache and lying about it.

I have been looking for information on how to ensure these are so for CENTOS and Ubuntu, but can't seem to find anything at all!

I want to be able to check these things and change them if needed.

Any and all input appreciated.

PLEASE NOTE: The actual hardware involved is VERY modest. The point is to get the most out of what hardware we do have, even though it's "not very serious hardware" from a broader perspective.

link|improve this question
How many disks? What types and speeds? What size is the DB? Which DB? How much RAM in the servers? – Sim Mar 31 '10 at 22:23
Hi Sim, I don't see any connection between the data you request in your queries and the information I am looking for, however: 1, 15k rpm, a few MB, Postgres, and 1gb and 4gb, depending on which of the two systems is involved. Note that I'm not seeking advice on databases in general, I'm just focused on O/S / Hardware issues in terms of making best use of minimal hardware. Thanks for your insights. – Richard T Apr 1 '10 at 20:27
I was just trying to get a scale of the hardware involved not only for myself but for others who may answer the question. – Sim Apr 1 '10 at 22:09
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown

Browse other questions tagged or ask your own question.