<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Meet Memcached: A Developer&#8217;s Best Friend</title>
	<atom:link href="http://blog.softlayer.com/2012/meet-memcached-a-developers-best-friend/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.softlayer.com/2012/meet-memcached-a-developers-best-friend/</link>
	<description>A Behind the Scenes Look at the Best Hosting Provider in the World</description>
	<lastBuildDate>Wed, 22 May 2013 17:40:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: David Mytton</title>
		<link>http://blog.softlayer.com/2012/meet-memcached-a-developers-best-friend/comment-page-1/#comment-41329</link>
		<dc:creator>David Mytton</dc:creator>
		<pubDate>Fri, 03 Aug 2012 09:42:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softlayer.com/?p=8765#comment-41329</guid>
		<description>Interestingly, MySQL 5.6.6 now includes memcached so you can mix and match queries depending on your query response time requirements, but still use the same underlying storage:

&quot;The MySQL server now includes the widely used memcached in-memory caching system, and a plugin that allows fast NoSQL-style access to InnoDB tables through the memcached protocol. This access method avoids the overhead of SQL parsing and constructing a query optimization plan. You can store the underlying data in a single InnoDB table, or spread it across multiple tables. You can read and write data through both memcached and SQL. For example, you can do fast single-key lookups through memcached get calls, and do statistical reports across all the data through SQL.&quot;

http://dev.mysql.com/doc/refman/5.6/en/news-5-6-6.html</description>
		<content:encoded><![CDATA[<p>Interestingly, MySQL 5.6.6 now includes memcached so you can mix and match queries depending on your query response time requirements, but still use the same underlying storage:</p>
<p>&#8220;The MySQL server now includes the widely used memcached in-memory caching system, and a plugin that allows fast NoSQL-style access to InnoDB tables through the memcached protocol. This access method avoids the overhead of SQL parsing and constructing a query optimization plan. You can store the underlying data in a single InnoDB table, or spread it across multiple tables. You can read and write data through both memcached and SQL. For example, you can do fast single-key lookups through memcached get calls, and do statistical reports across all the data through SQL.&#8221;</p>
<p><a href="http://dev.mysql.com/doc/refman/5.6/en/news-5-6-6.html" rel="nofollow">http://dev.mysql.com/doc/refman/5.6/en/news-5-6-6.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Legg</title>
		<link>http://blog.softlayer.com/2012/meet-memcached-a-developers-best-friend/comment-page-1/#comment-41315</link>
		<dc:creator>Dave Legg</dc:creator>
		<pubDate>Thu, 02 Aug 2012 23:30:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softlayer.com/?p=8765#comment-41315</guid>
		<description>It would be logical to declare $query before $key, and assign $key as $key = md5($query); to save issues when you come back later, and only edit the query in one of the two places it&#039;s currently located.

We used memcached to great effect at Neowin, every time a logged in user hits the front page, we load the latest news information from the database, and display it, saving a rendered copy of that section of the page into memcached. When a guest hits the page, they get the cached copy, and no database access is required. We constantly have a number of logged in users on the front page, so the cache is never stale. It&#039;s a great solution that lets us handle a heavy amount of traffic when we have popular stories (users coming in from reddit etc are usually guests, so the extra traffic adds hardly anything to the load)</description>
		<content:encoded><![CDATA[<p>It would be logical to declare $query before $key, and assign $key as $key = md5($query); to save issues when you come back later, and only edit the query in one of the two places it&#8217;s currently located.</p>
<p>We used memcached to great effect at Neowin, every time a logged in user hits the front page, we load the latest news information from the database, and display it, saving a rendered copy of that section of the page into memcached. When a guest hits the page, they get the cached copy, and no database access is required. We constantly have a number of logged in users on the front page, so the cache is never stale. It&#8217;s a great solution that lets us handle a heavy amount of traffic when we have popular stories (users coming in from reddit etc are usually guests, so the extra traffic adds hardly anything to the load)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
