[TYPO3] innoDB-tables in typo3

Ignatius Reilly ignatius.reilly at free.fr
Tue Sep 18 11:29:55 CEST 2007


Is it proof-tested to have _all_ tables of InnoDB type (core + ext)?

I suppose that would be the effect of a new install with MySQL directive
[mysqld]
default-storage-engine=innodb

Feedback welcome
Thanks

Dmitry Dulepov [typo3] thus spake on 2007-09-18 09:13:
> Hi!
> 
> Peter Falk wrote:
>> Some of the database tables in typo3 (from v. 4.1) is created as innoDB 
>> (syslog, fe_session a.m.). Is this a must or is it possible to change 
>> the tables to MyISAM?
> 
> It is not a requirement but there are reasons for this:
> - MyISAM locks the whole table for read and write when someone tries to write there. So if you have 100 clients and one of them writes data, other 99 wait. InnoDb allows reads while writes and returns only valid data. While it is not very important for syslog, it is very important for performance with cache_*, index_* and fe_* tables
> - When there are a lot of concurent writes, MyISAM tables may crash. You will never know that until you find that site works slow. Then you will find that one of cache_* failed and nothing is cached. With InnoDb carshes usually do not appear.
> 
> So feel free to change those tables to MyISAM locally of you want. But better keep them InnoDb.
> 


More information about the TYPO3-english mailing list