Recommend InnoDB tables for performance
Kiev1.org - March 11, 2008 - 22:10
| Project: | Drupal |
| Version: | 7.x-dev |
| Component: | mysql database |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Kiev1.org |
| Status: | active |
Jump to:
Description
tables sessions, node_counter and cache and all must be not MYISAM - tebles must be INNODB, otherwise the loaded site will be slow
#1
This is not a bug, reassigning as a feature request.
#2
And all feature requests go against current dev.
#3
just tested
innodb was slower ... a LOT slower for sessions
no difference for other tables
#4
myisam lock table in the moment of record in her values - that a base, in not dependence on power of server, can serve in one moment to time only read one node from one user.
#5
Innodb provide transaction support, which very important for enterprise cms.
We can also adopt mix of innodb and myisam for performance.
--
Sharique
#6
Sessions can sometimes be broken by InnoDB usage, depending on configuration. In particular, there is a race condition in the current (6.1) upload module where in some cases the page load for the upload occurs BEFORE the session update completes with a list of uploaded files. When this occurs, the upload fails, sometimes with unusual results. If InnoDB is set, we should have a start transaction / commit wrapper around session updates.