Hi,
Data center says to tune MySql instead of using memcache.
Any thoughts?
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?
For performance? On 12 Dec 2014 21:35, "Keith Smith" techlists@phpcoderusa.com wrote:
Hi,
Data center says to tune MySql instead of using memcache.
Any thoughts?
-- Keith Smith -- [ Drupal support list | http://lists.drupal.org/ ]
Yes for performance. Active website with lots of content and lots of modules. I have extra RAM that can be used to tune Mysql.
On 2014-12-12 13:48, Muzaffer Tolga Ozses wrote:
For performance? On 12 Dec 2014 21:35, "Keith Smith" techlists@phpcoderusa.com wrote:
Hi,
Data center says to tune MySql instead of using memcache.
Any thoughts?
-- Keith Smith -- [ Drupal support list | http://lists.drupal.org/ [1] ]
Links:
it can be a balancing act. Even if you're not using the RAM, linux is probably using it for caching and look ahead buffers. i still think memcache is worth it. Just make sure to get the latest version and watch for memory leaks. Even with 8 large buffers there's a leak on ours and it just continually grows until it runs out of memory and crashes. I created a little script to monitor the instances and restart them automatically if one or more crashes.
-Don-
On 12/12/2014 3:09 PM, Keith Smith wrote:
Yes for performance. Active website with lots of content and lots of modules. I have extra RAM that can be used to tune Mysql.
On 2014-12-12 13:48, Muzaffer Tolga Ozses wrote:
For performance? On 12 Dec 2014 21:35, "Keith Smith" techlists@phpcoderusa.com wrote:
Hi,
Data center says to tune MySql instead of using memcache.
Any thoughts?
-- Keith Smith -- [ Drupal support list | http://lists.drupal.org/ [1] ]
Links:
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?
-
Don -
Keith Smith -
Metzler, David -
Muzaffer Tolga Ozses