[support] tune MySql instead of using memcache

[Metzler, David]

In general-- bad advice. 

Tuning MYSQL db is about making the database server not have to access disk as often for pages that are cached in database.  It Might have a similar affect to  memcache if and only if the MySQL server is the same as the database server.  The latency associated with communicating with an external MYSQL server will still be there. 

Memcache is about creating shared memory area that allows multiple PHP processes to share the same cached data, therefore reducing the RAM footprint on the web servers (in addition to eliminating redundant queries. The memory footprint for web servers without memcache will still be larger than servers with memcache.

Although both strategies are viable ways of improving performance and it's generally true that MySQL optimization should be done first (as it affects dynamic page generation as well as cached pages).  It is not true that mysql tuning is a viable substitute for memcache. 

Good luck... Dave. 

-----Original Message-----
From: support-bounces at drupal.org [mailto:support-bounces at drupal.org] On Behalf Of Keith Smith
Sent: Friday, December 12, 2014 11:35 AM
To: support at drupal.org
Subject: [support] tune MySql instead of using memcache


Hi,

Data center says to tune MySql instead of using memcache.

Any thoughts?

-- 
Keith Smith
-- 
[ Drupal support list | http://lists.drupal.org/ ]