Alexander Staubo wrote: > On 5/23/07, PFC <[EMAIL PROTECTED]> wrote: >> +-------------------+-------+----------+-----------------------------+ >> | Table | Op | Msg_type | Msg_text | >> +-------------------+-------+----------+-----------------------------+ >> | forum_bench.posts | check | warning | Table is marked as crashed | >> | forum_bench.posts | check | error | Found 588137 keys of 588135 | >> | forum_bench.posts | check | error | Corrupt | >> +-------------------+-------+----------+-----------------------------+ > > I find it hard to believe that this is MySQL's fault and not some > problem with your setup. Granted, MySQL is a pretty bad database, but > it's not *that* bad -- your example implies that heavily MyISAM-based > (you don't say whether this is MyISAM or InnoDB) sites such as > Slashdot and Flickr should be falling over every hour.
I'm not going to comment on who's fault it is, but the OP quoted 100 updates and 600 selects per *second*. I can't imagine Flickr or Slashdot (which is heavily csched for reading) are under anything like that sort of constant load. Regards, Dave. ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
