<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Pablowe &#187; MySQL Performance</title>
	<atom:link href="http://www.pablowe.net/category/mysql-performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pablowe.net</link>
	<description>%&#62; random tech;</description>
	<lastBuildDate>Fri, 30 Sep 2011 16:54:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Connecting to HandlerSocket with localhost vs. 127.0.0.1</title>
		<link>http://www.pablowe.net/2011/02/connecting-to-handlersocket-with-localhost-vs-127-0-0-1/</link>
		<comments>http://www.pablowe.net/2011/02/connecting-to-handlersocket-with-localhost-vs-127-0-0-1/#comments</comments>
		<pubDate>Sat, 05 Feb 2011 04:56:22 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[HandlerSocket]]></category>
		<category><![CDATA[MySQL Performance]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Random Tech]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=628</guid>
		<description><![CDATA[Using Net::HandlerSocket, here are some fun numbers for a single connection (open &#038; close). When connecting to &#8220;localhost&#8221;, here&#8217;s the strace: open("/etc/hosts", O_RDONLY) = 3 fcntl(3, F_GETFD) = 0 fcntl(3, F_SETFD, FD_CLOEXEC) = 0 fstat(3, {st_mode=S_IFREG&#124;0644, st_size=187, ...}) = 0 mmap(NULL, 4096, PROT_READ&#124;PROT_WRITE, MAP_PRIVATE&#124;MAP_ANONYMOUS, -1, 0) = 0x2b909a1a3000 read(3, "# Do not remove the following [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2011/02/connecting-to-handlersocket-with-localhost-vs-127-0-0-1/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>The Awkward Stage of Scaling</title>
		<link>http://www.pablowe.net/2008/10/the-awkward-stage-of-scaling/</link>
		<comments>http://www.pablowe.net/2008/10/the-awkward-stage-of-scaling/#comments</comments>
		<pubDate>Fri, 10 Oct 2008 02:19:57 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Performance]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Data Sharding]]></category>
		<category><![CDATA[Functional Partitioning]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=134</guid>
		<description><![CDATA[A lot of my clients are in a position where their database performance is deteriorating but they are not &#8220;big enough&#8221; (or not willing/able to) explore sharding all of their data structures. They&#8217;re too big for the solution to be adding another read slave, but too small to justify the resources for re-designing their architecture. [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/10/the-awkward-stage-of-scaling/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Dangers of Having status fields</title>
		<link>http://www.pablowe.net/2008/08/the-dangers-of-having-status-fields/</link>
		<comments>http://www.pablowe.net/2008/08/the-dangers-of-having-status-fields/#comments</comments>
		<pubDate>Wed, 27 Aug 2008 19:59:02 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Performance]]></category>
		<category><![CDATA[MySQL Schema Design]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=11</guid>
		<description><![CDATA[Having a status column is very common in databases today. It can be used to denote a user status: CREATE TABLE IF NOT EXISTS `user` ( `user_id` int(10) unsigned NOT NULL auto_increment, `email` varchar(32) NOT NULL, `pw_hash` char(40) NOT NULL COLLATE latin1_general_cs, `status` enum('PENDING', 'ACTIVE', 'DISABLED') default 'PENDING', `date_created` timestamp NOT NULL default CURRENT_TIMESTAMP, PRIMARY [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/08/the-dangers-of-having-status-fields/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Must we always escape values?</title>
		<link>http://www.pablowe.net/2008/08/must-we-always-escape-values/</link>
		<comments>http://www.pablowe.net/2008/08/must-we-always-escape-values/#comments</comments>
		<pubDate>Mon, 18 Aug 2008 18:17:17 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Performance]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=35</guid>
		<description><![CDATA[One of the cardinal rules of writing web applications is to escape user-generated input with functions like PHP&#8217;s real_escape_string. This is a great rule, but one that can have a negative impact on your application&#8217;s performance if used unnecessarily. For instance, when querying data with an integer parameter that is passed internally (not user-generated): $query [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/08/must-we-always-escape-values/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Query Performance Improvement Process</title>
		<link>http://www.pablowe.net/2008/08/the-query-performance-improvement-process/</link>
		<comments>http://www.pablowe.net/2008/08/the-query-performance-improvement-process/#comments</comments>
		<pubDate>Sun, 03 Aug 2008 22:28:08 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Performance]]></category>
		<category><![CDATA[MySQL Query Optimization]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=39</guid>
		<description><![CDATA[The purpose of this post is to outline a general flow-chart for improving the performance of queryies in MySQL. Much has been written on using EXPLAIN to optimize queries, but there is a whole process that should be followed in order to maximize the effectiveness of query performance tuning. Following is a visual flow-chart of [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/08/the-query-performance-improvement-process/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Nagios as a MySQL Performance Profiler</title>
		<link>http://www.pablowe.net/2008/06/using-nagios-as-a-mysql-performance-profiler/</link>
		<comments>http://www.pablowe.net/2008/06/using-nagios-as-a-mysql-performance-profiler/#comments</comments>
		<pubDate>Tue, 17 Jun 2008 23:37:16 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[MySQL Performance]]></category>
		<category><![CDATA[Nagios]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=6</guid>
		<description><![CDATA[Everybody knows than Nagios can be used as a service monitor to monitor things like Load Averages, MySQL Replication Status, RAID Array States, etc&#8230; Fewer know that there are plug-ins to monitor MySQL Performance Status, such as check_mysql_perf. Fewer still utilize Nagios&#8217; built-in triggering mechanism to execute an additional script on the event of a [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/06/using-nagios-as-a-mysql-performance-profiler/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

