[TYPO3-dev] Typo3 4.1 - Server crashes
Martin Kutschker
Martin.Kutschker at n0spam-blackbox.net
Mon Mar 26 18:21:53 CEST 2007
Elmar HInz schrieb:
> Am Mon, 26 Mar 2007 15:04:39 +0300 schrieb Dmitry Dulepov:
>
>
>>You forget that innodb works much better with locks, which is esential
>>for index tables...
>
>
> That is one point, but is it that relevant for TYPO3 usage at all?
>
> a) Locks work in the moment of writing. 99.9% of use of index tables -
> in all TYPO3 tables - is reading. They need to be optimized for that,
> rarely for secure transactions.
Dmitry doesn't talk about explicit locks by the application but implicit
locks that the DB server sets itself. Mysql locks a table when it writes to
it. So less locks on the whole table means more concurrent reads to this table.
> c) MyIsam Tables are written in timly order, so that the bits and bytes
> don't need to be moved around. InnoDB are written in order of the primary
> key, wich requires additional mechanism to reorder the data. Also a
> resource eater.
>
> From this thoughts I would not expect performance gains by InnoDB,
> rather the opposite. But theory is one thing. The other should be
> benchmarking.
Dmitry has repeatedly posted his success in using InnoDB in high-load
situations where Myisam failed.
Masi
More information about the TYPO3-dev
mailing list