<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Performance Tuning on Justin Carmony</title>
		<link>https://www.justincarmony.com/tags/performance-tuning/</link>
		<description>Recent content in Performance Tuning on Justin Carmony</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Wed, 02 Feb 2011 07:12:35 +0000</lastBuildDate>
		
			<atom:link href="https://www.justincarmony.com/tags/performance-tuning/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>MySQL Stored Procedure, NAME_CONST, and Character Sets</title>
				<link>https://www.justincarmony.com/2011/02/02/mysql-stored-procedure-name_const-and-character-sets/</link>
				<pubDate>Wed, 02 Feb 2011 07:12:35 +0000</pubDate>
				<guid>https://www.justincarmony.com/2011/02/02/mysql-stored-procedure-name_const-and-character-sets/</guid>
				<description>&lt;p&gt;&lt;a href=&#34;https://www.justincarmony.com/images/wp/2011/02/mysql_logo.gif&#34;&gt;&lt;img src=&#34;https://www.justincarmony.com/images/wp/2011/02/mysql_logo.gif&#34; alt=&#34;&#34; title=&#34;mysql_logo&#34;&gt;&lt;/a&gt;For a Project I had helped work on, they recently needed to move servers and in the process upgraded from MySQL 5.0 to MySQL 5.1.41. They ran into some quirks with 5.1 and I thought I would document our work-a-rounds for them.&lt;/p&gt;&#xA;&lt;p&gt;We were having serious performance problems with a Stored Procedure that would be called by a Windows Client on thousands of machines. Before on 5.0 it would take under 0.02 seconds, and now it was taking 25-35 seconds. In this stored procedure we would call a query something like this:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
