<?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/"
	>

<channel>
	<title>Pablowe</title>
	<atom:link href="http://www.pablowe.net/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pablowe.net</link>
	<description>%&#62; random tech;</description>
	<pubDate>Sat, 03 Jan 2009 22:55:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Nagios3 on CentOS: Quick Install Script</title>
		<link>http://www.pablowe.net/2009/01/03/nagios3-on-centos-quick-install-script/</link>
		<comments>http://www.pablowe.net/2009/01/03/nagios3-on-centos-quick-install-script/#comments</comments>
		<pubDate>Sat, 03 Jan 2009 22:55:33 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
		
		<category><![CDATA[Random Tech]]></category>

		<category><![CDATA[Nagios]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=171</guid>
		<description><![CDATA[As part my job, I find myself doing Nagios installs on a somewhat regular basis.  The following is a quick guide on installing Nagios 3 on CentOS, distilled from the official Nagios docs.  It is meant to be copied and run as a shell script (you should only have to update the passwords):

#!/bin/sh

# [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2009/01/03/nagios3-on-centos-quick-install-script/feed/</wfw:commentRss>
		</item>
		<item>
		<title>ATTN: Wordpress Theme &#038; Plug-In Developers</title>
		<link>http://www.pablowe.net/2008/10/29/attn-wordpress-theme-plug-in-developers/</link>
		<comments>http://www.pablowe.net/2008/10/29/attn-wordpress-theme-plug-in-developers/#comments</comments>
		<pubDate>Thu, 30 Oct 2008 04:20:44 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
		
		<category><![CDATA[Performance]]></category>

		<category><![CDATA[Random Tech]]></category>

		<category><![CDATA[Minify]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=154</guid>
		<description><![CDATA[Please minify all JavaScript and CSS files.  The size of the main page at pablowe.net was reduced by 20% by this simple, 30-second act.
CSS::Minify
JavaScript::Minifier
Thank You!
]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/10/29/attn-wordpress-theme-plug-in-developers/feed/</wfw:commentRss>
		</item>
		<item>
		<title>OmniSQL 0.0.7 Released</title>
		<link>http://www.pablowe.net/2008/10/28/omnisql-007-released/</link>
		<comments>http://www.pablowe.net/2008/10/28/omnisql-007-released/#comments</comments>
		<pubDate>Tue, 28 Oct 2008 17:31:35 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
		
		<category><![CDATA[MySQL]]></category>

		<category><![CDATA[MySQL Administration]]></category>

		<category><![CDATA[OmniSQL]]></category>

		<category><![CDATA[Data Sharding]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=151</guid>
		<description><![CDATA[OmniSQL (a command line tool for DBAs needing to issue ad-hoc queries against sharded data) version 0.0.7 is officially released.
Instead of logging in separately to multiple databases to issue the same query, groups of databases can be specified in a configuration file and queries will be automatically issued against all targeted MySQL instances.
Let me know [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/10/28/omnisql-007-released/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The Awkward Stage of Scaling</title>
		<link>http://www.pablowe.net/2008/10/09/the-awkward-stage-of-scaling/</link>
		<comments>http://www.pablowe.net/2008/10/09/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 [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/10/09/the-awkward-stage-of-scaling/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Managing MySQL Configuration Files</title>
		<link>http://www.pablowe.net/2008/09/03/managing-mysql-configuration-files/</link>
		<comments>http://www.pablowe.net/2008/09/03/managing-mysql-configuration-files/#comments</comments>
		<pubDate>Wed, 03 Sep 2008 21:08:40 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
		
		<category><![CDATA[MySQL]]></category>

		<category><![CDATA[MySQL Administration]]></category>

		<category><![CDATA[MySQL Configuration Management]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=80</guid>
		<description><![CDATA[It is good practice to manage changes to MySQL configuration files (/etc/my.cnf) by using a version control system.  I usually use a home-brewed (not brewed by me!) svn+cfengine application to propagate my.cnf (and other configuration file) changes to defined classes of machines (classes are based on application role, replication role, etc).
When managing hundreds of [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/09/03/managing-mysql-configuration-files/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The Dangers of Having status fields</title>
		<link>http://www.pablowe.net/2008/08/27/the-dangers-of-having-status-fields/</link>
		<comments>http://www.pablowe.net/2008/08/27/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 KEY (`user_id`),
UNIQUE KEY `idx_email` (`email`)
);
or user-uploaded [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/08/27/the-dangers-of-having-status-fields/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Must we always escape values?</title>
		<link>http://www.pablowe.net/2008/08/18/must-we-always-escape-values/</link>
		<comments>http://www.pablowe.net/2008/08/18/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 [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/08/18/must-we-always-escape-values/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Improving WordPress Performance with Basic MySQL Maintenance</title>
		<link>http://www.pablowe.net/2008/08/17/improving-wordpress-performance-with-basic-mysql-maintenance/</link>
		<comments>http://www.pablowe.net/2008/08/17/improving-wordpress-performance-with-basic-mysql-maintenance/#comments</comments>
		<pubDate>Sun, 17 Aug 2008 21:53:57 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
		
		<category><![CDATA[Random Tech]]></category>

		<category><![CDATA[Wordpress Performance]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=56</guid>
		<description><![CDATA[If your blog is anything like mine, the vast majority of comments are spam.   Most blogs have at least a 50% ratio of spam-to-valid comments, and Pablowe has a 99.4% ratio (which is probably why there are so many Anti-Spam plugins for WordPress).  
One of the most oft-executed queries (based on the [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/08/17/improving-wordpress-performance-with-basic-mysql-maintenance/feed/</wfw:commentRss>
		</item>
		<item>
		<title>OmniSQL 0.0.6 Released</title>
		<link>http://www.pablowe.net/2008/08/13/omnisql-006-released/</link>
		<comments>http://www.pablowe.net/2008/08/13/omnisql-006-released/#comments</comments>
		<pubDate>Wed, 13 Aug 2008 15:42:41 +0000</pubDate>
		<dc:creator>rlowe</dc:creator>
		
		<category><![CDATA[MySQL]]></category>

		<category><![CDATA[OmniSQL]]></category>

		<category><![CDATA[Data Sharding]]></category>

		<guid isPermaLink="false">http://www.pablowe.net/?p=44</guid>
		<description><![CDATA[OmniSQL (a command line tool for DBAs needing to issue ad-hoc queries against sharded data) version 0.0.6 is officially released.  
Instead of logging in separately to multiple databases to issue the same query, groups of databases can be specified in a configuration file and queries will be automatically issued against all targeted MySQL instances. [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/08/13/omnisql-006-released/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The Query Performance Improvement Process</title>
		<link>http://www.pablowe.net/2008/08/03/the-query-performance-improvement-process/</link>
		<comments>http://www.pablowe.net/2008/08/03/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 [...]]]></description>
		<wfw:commentRss>http://www.pablowe.net/2008/08/03/the-query-performance-improvement-process/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
