I don't see a problem with IDE drives. Your drive access patterns are pretty straight forward. SCSI's big advantage is command queueing, which may not even come into play with your access patterns.
Whatever file system you use, I would most definitely use journaling. First and foremost you need the system in a good state, then the DB. Journaling in the file system will also help in keeping the database intact. Raw partitions would buy you so little performance gain, it's really not worth the hassle. On the flip side, software mirroring of two IDE drives would give you such a little performance hit, it would be worth it for safety. And you'll get better read performance to boot.
InnoDB would probably be better than MyISAM since InndoDB supports transactions.
On Mar 30, 2005, at 2:47 AM, Florin Andrei wrote:
Again the logging server i mentioned before: it's like syslog logging to a DB, lots of INSERTs, perhaps a few SELECTs every now and then, the tables are append-only and are rotated about once a day. For reasons that i am not going to discuss here, the machine has no uninterruptible power supply. Therefore, if the power goes down, bad things might happen to the database. Also, i don't have money for funky solutions such as solid-state disks. In fact, the disks will most likely be IDE (not even SCSI).
What are the techniques that work best in such a situation to increase the chances for the database to survive a crash in a consistent state? Loosing a few recent INSERTs is not a problem (since some data will not be logged anyway while the server is down), but the DB in an inconsistent state is a big problem (the system has to boot up again unattended).
I do not want to do such extreme things like turning off the write cache on the disk, because that would probably kill the performance. But how about Ext3 with data=journal? Using InnoDB would be better than MyISAM? How about raw partitions? Any other tips?
-- Florin Andrei
http://florin.myip.org/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
-- Brent Baisley Systems Architect Landover Associates, Inc. Search & Advisory Services for Advanced Technology Environments p: 212.759.6400/800.759.0577
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
