Originally posted by administrator
View Post
Various folks have done it with Drupal, usually needing to hack it a bit to do certain things in a more InnoDB friendly way, and the current development version (V7 - the next major release) uses InnoDB as the default.
Yes, what suits Drupal won't necessarily fit VBulletin requirements, but there's some good experience out there which is probably highly relevant.
Converting your Drupal MySQL database from MyISAM to InnoDB - do follow the links here
In particular, search tables are probably best left as MyISAM, and the default buffer pool sizes for InnoDB are pitifully low.
Referring back to:
Originally posted by realityhack
View Post
I've just changed all my InnoDB tables back to MyISAM because:
a) InnoDB seemed to use more memory
b) InnoDB causes load to go up - changing back to MyISAM dropped my loads down by 90%!!!
c) InnoDB used more hard disk space
d) InnoDB is slower than MyISAM
a) InnoDB seemed to use more memory
b) InnoDB causes load to go up - changing back to MyISAM dropped my loads down by 90%!!!
c) InnoDB used more hard disk space
d) InnoDB is slower than MyISAM
- Yes it can use more memory, but that also gives faster performance
- In one case I read about, this was because it was actually doing more useful work - i.e. the bottleneck had shifted
- dumping the MyISAM database by primary key apparently solves this
- Way too general a statement - it depends on what it's being asked to do
MySQL Engines: MyISAM vs. InnoDB again follow the links
MySQL InnoDB: performance gains as well as some pitfalls - take note of the stuff about locking, autoincrement fields and SELECT (*) COUNT (SELECT (*) MAX is better if that fits the app).
InnoDB Performance Tuning
I got this little lot from Googling "drupal 7 innodb" - there were plenty more hits.
Leave a comment: