i would be dubious unless they offer mysql on a flash drive. I've tuned mysql caching, but it still seems slower than memcache. the larger the site the less chance the queries are in memory. I have memcache broken into 8 partitions too. On 12/12/2014 2:34 PM, Keith Smith wrote:

Hi,

Data center says to tune MySql instead of using memcache.

Any thoughts?

-- -Don Pickerel- Fane Software

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@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Keith Smith Sent: Friday, December 12, 2014 11:35 AM To: support@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/ ]