That went mostly well. We got two dead servers assembled into one that'll probably work, or maybe not. It was installing slower than slowly over the network. Robert set it up to redirect the BIOS to the serial port and we hooked it into the console server so he'll try installing it from home later. We also hooked the new switch up to the console. Cyclades++.
We got all the disks in the new RAID working. It'll be very very cool when we start actually using them. The hardware RAID-5 with the 120GB disks we are using now isn't performing well at all.
While taking disks out and checking the connectors Robert pulled the disk we thought was an extra extra hot spare for the existing RAID only to minutes later realize it had a swap partition on it. Ooops!
MySQL was apparently swapped a bit because it crashed with a really really long dump to the log and some corrupted MyISAM indexes. All the InnoDB tables came up fine though. When InnoDB first came out I was much more comfortable with MyISAM because how simple it was. I'm only going to use MyISAM in the future when the particular performance characteristics of it are needed.
What, in a nutshell, are the differences in characteristics between the two table types?
ReplyDeleteDavid,
ReplyDeleteInnoDB: Transactions, row locking, foreign keys, faster for mixed read/write applications that'd give contention with MyISAM.
MyISAM: (Usually) faster for (almost) exclusively read applications, support the GIS extensions, simpler administration.
- ask