<?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"
	>
<channel>
	<title>Comments on: Personal Opinion: Half-baked = false analogy</title>
	<atom:link href="http://blogs.mysql.com/peterg/2008/05/19/personal-opinion-half-baked-false-analogy/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.mysql.com/peterg/2008/05/19/personal-opinion-half-baked-false-analogy/</link>
	<description>By MySQL development-department workers</description>
	<pubDate>Wed, 25 Nov 2009 00:32:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Jay Pipes</title>
		<link>http://blogs.mysql.com/peterg/2008/05/19/personal-opinion-half-baked-false-analogy/#comment-4</link>
		<dc:creator>Jay Pipes</dc:creator>
		<pubDate>Mon, 19 May 2008 17:22:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.mysql.com/peterg/2008/05/19/personal-opinion-half-baked-false-analogy/#comment-4</guid>
		<description>Heh, you have a good point about the linguistic difference between "drunkard's walk" and "half baked"...

Here is the proof you ask for:

MySQL stored routines:  the compile cache is on the connection thread, not in a global cache, so stored procedures are re-compiled on each connection thread, which is a waste of resources (even if such connection-caches reduce global lock contention).

AFAIU, this design was chosen because it was considered too much of an overhaul to actually re-architect the pieces of the server kernel/runtime which would be necessary to implement a global compile cache, and thus we have a "half-baked" feature that although it works, isn't efficient and causes perhaps more problems than it solves.

-jay</description>
		<content:encoded><![CDATA[<p>Heh, you have a good point about the linguistic difference between &#8220;drunkard&#8217;s walk&#8221; and &#8220;half baked&#8221;&#8230;</p>
<p>Here is the proof you ask for:</p>
<p>MySQL stored routines:  the compile cache is on the connection thread, not in a global cache, so stored procedures are re-compiled on each connection thread, which is a waste of resources (even if such connection-caches reduce global lock contention).</p>
<p>AFAIU, this design was chosen because it was considered too much of an overhaul to actually re-architect the pieces of the server kernel/runtime which would be necessary to implement a global compile cache, and thus we have a &#8220;half-baked&#8221; feature that although it works, isn&#8217;t efficient and causes perhaps more problems than it solves.</p>
<p>-jay</p>
]]></content:encoded>
	</item>
</channel>
</rss>
