<?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: Gawker Media to dump SixApart?</title>
	<atom:link href="http://www.duncanriley.com/2006/07/03/gawker-media-to-dump-sixapart/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.duncanriley.com/2006/07/03/gawker-media-to-dump-sixapart/</link>
	<description>blogging is not a spectator sport</description>
	<lastBuildDate>Fri, 19 Mar 2010 06:57:22 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sam Jackson</title>
		<link>http://www.duncanriley.com/2006/07/03/gawker-media-to-dump-sixapart/comment-page-1/#comment-13830</link>
		<dc:creator>Sam Jackson</dc:creator>
		<pubDate>Mon, 10 Jul 2006 19:54:33 +0000</pubDate>
		<guid isPermaLink="false">http://duncanriley.com/2006/07/03/gawker-media-to-dump-sixapart/#comment-13830</guid>
		<description>WP can be deadly to the sql backend if you aren&#039;t careful--lazy plugins making too many calls, etc. Especially on new WP2 AJAX-ridden themes, it can be heady. But with careful optimization of the scripts you can do quite well. Optimize CSS by removing whitespace and comments, so forth and so on. You can shave off a lot of fat and it will be fine.</description>
		<content:encoded><![CDATA[<p>WP can be deadly to the sql backend if you aren&#8217;t careful&#8211;lazy plugins making too many calls, etc. Especially on new WP2 AJAX-ridden themes, it can be heady. But with careful optimization of the scripts you can do quite well. Optimize CSS by removing whitespace and comments, so forth and so on. You can shave off a lot of fat and it will be fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anil</title>
		<link>http://www.duncanriley.com/2006/07/03/gawker-media-to-dump-sixapart/comment-page-1/#comment-12992</link>
		<dc:creator>Anil</dc:creator>
		<pubDate>Thu, 06 Jul 2006 00:20:50 +0000</pubDate>
		<guid isPermaLink="false">http://duncanriley.com/2006/07/03/gawker-media-to-dump-sixapart/#comment-12992</guid>
		<description>There&#039;s sites larger than the individual Gawker ones (BusinessWeek, Washington Post, Huffington Post, Gothamist, etc.) running on MT, so it&#039;s certainly not that MT can&#039;t scale to run big sites.</description>
		<content:encoded><![CDATA[<p>There&#8217;s sites larger than the individual Gawker ones (BusinessWeek, Washington Post, Huffington Post, Gothamist, etc.) running on MT, so it&#8217;s certainly not that MT can&#8217;t scale to run big sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: duncan</title>
		<link>http://www.duncanriley.com/2006/07/03/gawker-media-to-dump-sixapart/comment-page-1/#comment-12811</link>
		<dc:creator>duncan</dc:creator>
		<pubDate>Tue, 04 Jul 2006 01:10:00 +0000</pubDate>
		<guid isPermaLink="false">http://duncanriley.com/2006/07/03/gawker-media-to-dump-sixapart/#comment-12811</guid>
		<description>The problem I found in terms of the backend was more from a hosting point, particularly with the Blog Herald, where as now we&#039;ve had relatively few issues with WordPress, even at 20 million page views a month...and that&#039;s only on 3 boxes! We know a lot more about hosting today than I did even 6 months ago, so I think it is scalable, however there is little doubt with either system that there is effeciencies that could be made.</description>
		<content:encoded><![CDATA[<p>The problem I found in terms of the backend was more from a hosting point, particularly with the Blog Herald, where as now we&#8217;ve had relatively few issues with WordPress, even at 20 million page views a month&#8230;and that&#8217;s only on 3 boxes! We know a lot more about hosting today than I did even 6 months ago, so I think it is scalable, however there is little doubt with either system that there is effeciencies that could be made.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Krug</title>
		<link>http://www.duncanriley.com/2006/07/03/gawker-media-to-dump-sixapart/comment-page-1/#comment-12756</link>
		<dc:creator>David Krug</dc:creator>
		<pubDate>Mon, 03 Jul 2006 14:16:03 +0000</pubDate>
		<guid isPermaLink="false">http://duncanriley.com/2006/07/03/gawker-media-to-dump-sixapart/#comment-12756</guid>
		<description>Really I think its because MT doesn&#039;t hold up well, and neither does wordpress to high traffic blogs. Even at 4k a day I&#039;m worried about one of my new sites. The database starts acting funky and how is WP going to handle at 40k? 

I mean the BlogHerald ran alright with its readership but not great. 

I think someone could come out with a better properietary solution for high traffic blogs.</description>
		<content:encoded><![CDATA[<p>Really I think its because MT doesn&#8217;t hold up well, and neither does wordpress to high traffic blogs. Even at 4k a day I&#8217;m worried about one of my new sites. The database starts acting funky and how is WP going to handle at 40k? </p>
<p>I mean the BlogHerald ran alright with its readership but not great. </p>
<p>I think someone could come out with a better properietary solution for high traffic blogs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
