I wasn't doubting your advice, or experience. The DBs that I develop will /never/ reach the performance requirements that your work does. It's just a tad confusing when you suggest that MyISAM might be preferred for a specific reason, when the best that I can find is full-text indexing. That is all.
And Pete, shove it up your arse. Love'n'cuddles, ect.
But then there's the performance problem that Mark had right at the very start. If I have this correct, MyISAM would be useful for a DB-based site where SELECT queries are the norm, but InnoDB for transactional security and relational integrity (I usually fudge that in the DB design and script). I guess you can choose different engines for the same site, depending on whether there will be more/less SELECT queries.
From a personal POV, I could care less about full text indexing. Perhaps I shouldn't be so dismissive of it though.
No, you didn't read what I posted in reply to Mark originally.
myisam performance is not just down to the number of SELECTs you have, it's more complex than that and involves taking into account which of your queries will lock the entire table as they execute and which other queries may be running concurrently.
Any SELECTs involving joins, UPDATEs and INSERTs (in certain curcumstances) will cause the entire table to be write locked which may or may not be a problem depending on what else is going on at the same time.
For Marks tests, he seems to be doing quite intensive operations on a relatively large data set of 4.6m rows. I would hazard a guess that if he introduced some other query types on that data set to run concurrently (as one might get on a high transaction system) he would see some undesired locking situations.
MyISAM has a concurrent insert mode, which you can play with to allow it to append records to the end of the data file (rather than hunting for a gap in the middle of the data file) if there is another SELECT in progress, thus avoiding locking that SELECT out.
You can tailor it to your individual circumstances.
http://dev.mysql.com/doc/refman/5.1/en/concurrent-inserts.html
It's kinda like saying I couldn't care less, but in a more sarcastic way as Xen said. I guess it should be 'I could care less, but not without trying hard' or some such but, frankly, I could care less.
I have no idea whether it's American usage. It's not Swiss German, that's for sure.
I could care less.
(hippo)
I like it as it is. (Even thought I feel dirty that it might be merkan.)