[consulting] Drupal server requirements

[Michael Haggerty]

Why not cluster MySQL instead, do all your writes to a single database and
reads from one or more mirrored dbs? If you set it up right, the latency
should be measured in milliseconds. Even InnoDB can get flooded.

M

> -----Original Message-----
> From: John Handelaar
> Sent: Tuesday, March 28, 2006 7:03 AM
> To: A list for Drupal consultants and Drupal service/hosting providers
> Subject: Re: [consulting] Drupal server requirements
> 
> This all derives from analysing MBR.org to death when it hit 
> the wall earlier this year (at the 2m-pages-per- month mark, 
> roughly, on a server running Apache1.3 and MySQL 4.1 with 1Gb 
> of memory).
> 
> I'm explaining it with the 3-step logic above, which if you 
> read it carefully, describes a process which
> *will* always fail under high load.
> 
> It's not even about the read/write ratio.
> 
> When you have a very high volume of READs, even one comment 
> posting will cause a traffic jam at the database side because 
> of the table locking.
> 
> I'm suggesting InnoDB because with Drupal, in almost every 
> case, that engine will use row-level locking only and hence 
> *not* stall all pending reads.  Any other engine capable of 
> row-level locking will also help.
> 
> --
> -------------------------------------------
> John Handelaar
> 
> E  john at handelaar.org    T +353 21 427 9033
> M  +353 85 748 3790    http://handelaar.org
> -------------------------------------------