[horde] mySQL storage engine

[Abu Hurayrah]

Actually, MySQL locks tables for writing on UPDATEs to MyISAM tables as 
well.  SELECTs can occur concurrently with INSERTs if there are no 
deleted rows in a MyISAM table, otherwise MySQL will lock the table 
while it attempts to INSERT a record into a space created by a previous 
DELETE.  This can be avoided by not deleting records and/or optimizing 
your tables to clear out any holes.  In general, MyISAM is faster for 
reading, by what was said about row-level locking for InnoDB tables is 
very useful for data that needs to be both updated & read concurrently.

As an example, MediaWiki, the software that operates Wikipedia, runs 
almost exclusively on InnoDB tables because the nature of the site 
requires that SELECTs & UPDATEs be allowed to happen concurrently.

Jan Schneider wrote:
> Zitat von Liam Hoekenga <liamr at deathstar.org>:
>
>> You're probably going to want to use InnoDB, for the row level 
>> locking.  MyISAM only has table level locking, and that can leave the 
>> DB waiting for locks a lot of the time.
>
> But this is only important where we lock tables, ie. only the session 
> handler table at the moment.
>
>> Kevin Conley wrote:
>>> What is the recommended engine for mySQL when using HORDE/IMP/TURBA?
>>>
>>> We have 4 front end webservers using one mySQL server via network 
>>> connections.
>>>
>>> Thanks
>>>
>>> Kevin
>>>
>>
>> --Horde mailing list - Join the hunt: http://horde.org/bounties/#horde
>> Frequently Asked Questions: http://horde.org/faq/
>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>>
>
>
>
> Jan.
>
> --Do you need professional PHP or Horde consulting?
> http://horde.org/consulting/
>
> --Horde mailing list - Join the hunt: http://horde.org/bounties/#horde
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org