I'd say that if your database can fit on the SCSI drive you can afford, there is no reason for not choosing SCSI. Or, hec, if it's a really small database, why not ramdist?
In regard to your question about whether it confirms a write before commiting a transaction. First of all, check to see if there are any notes about MySQL's behavior on your platform: http://www.mysql.com/doc/O/p/Operating_System_Specific_Notes.html you can also refer to the optimization guide. http://www.mysql.com/doc/M/y/MySQL_Optimisation.html I don't _think_ it checks to make sure the write actually happens before confirming the transaction, but I'm not certain. On Tuesday 20 November 2001 08:52 am, Thomas S. Iversen wrote: > Hi > > This is not an atempt to start a flamewar!! > > We're about to build a db server for educational purposes. Running 150+ > databases pr. semester. Nothing big, nothing demanding when looking at a > single database, but combined it may give some load (might be a lot of > concurrent activity during classes, none afterwords, etc). > > Back to the question: we're on a limited budget, and have to choose > between either inexpensive but large IDE disk or fast but small SCSI > disks. The machine has 1GB memory. First thought would be IDE disks since > we have enough memory to cache the DBs. > > Question: Does a write transaction in mysql wait for the disk to actually > write the data onto the platter (thereby eliminating our cache), or > doesn't it care about the data hitting the disk before returning (leaving > it to the OS)? If it's the first we might opt for SCSI, if it's the > latter we'll go for IDE. > > Thanks for your time. > > Regards Thomas, Denmark --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
