<?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: Speeding up file processing with Unix commands</title>
	<atom:link href="http://handyfloss.net/2008.02/speeding-up-file-processing-with-unix-commands/feed/" rel="self" type="application/rss+xml" />
	<link>http://handyfloss.net/2008.02/speeding-up-file-processing-with-unix-commands/</link>
	<description>Because FLOSS is handy, isn&#039;t it?</description>
	<lastBuildDate>Wed, 01 Feb 2012 20:23:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Summary of my Python optimization adventures &#171; handyfloss</title>
		<link>http://handyfloss.net/2008.02/speeding-up-file-processing-with-unix-commands/comment-page-1/#comment-5410</link>
		<dc:creator>Summary of my Python optimization adventures &#171; handyfloss</dc:creator>
		<pubDate>Thu, 18 Sep 2008 12:43:58 +0000</pubDate>
		<guid isPermaLink="false">http://handyfloss.net/?p=296#comment-5410</guid>
		<description>[...] the first one I spoke about saving memory by reading line-by-line, instead of all-at-once, and in the second one I recommended using Unix [...]</description>
		<content:encoded><![CDATA[<p>[...] the first one I spoke about saving memory by reading line-by-line, instead of all-at-once, and in the second one I recommended using Unix [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Speeding up file processing with Unix commands &#171; handyfloss</title>
		<link>http://handyfloss.net/2008.02/speeding-up-file-processing-with-unix-commands/comment-page-1/#comment-5324</link>
		<dc:creator>Speeding up file processing with Unix commands &#171; handyfloss</dc:creator>
		<pubDate>Wed, 17 Sep 2008 08:51:32 +0000</pubDate>
		<guid isPermaLink="false">http://handyfloss.net/?p=296#comment-5324</guid>
		<description>[...] Entry available at: http://handyfloss.net/2008.02/speeding-up-file-processing-with-unix-commands/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Entry available at: <a href="http://handyfloss.net/2008.02/speeding-up-file-processing-with-unix-commands/" rel="nofollow">http://handyfloss.net/2008.02/speeding-up-file-processing-with-unix-commands/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Super Coco</title>
		<link>http://handyfloss.net/2008.02/speeding-up-file-processing-with-unix-commands/comment-page-1/#comment-109</link>
		<dc:creator>Super Coco</dc:creator>
		<pubDate>Sun, 17 Feb 2008 17:19:07 +0000</pubDate>
		<guid isPermaLink="false">http://handyfloss.net/?p=296#comment-109</guid>
		<description>I usually create shell scripts involving a lot of command line utilities (awk, grep, sed, wc...) to process very large files (sometime as large as several GB) and I&#039;d expect the scripts to very veeeery slow, but it often surprises me how fast they can be :-O</description>
		<content:encoded><![CDATA[<p>I usually create shell scripts involving a lot of command line utilities (awk, grep, sed, wc&#8230;) to process very large files (sometime as large as several GB) and I&#8217;d expect the scripts to very veeeery slow, but it often surprises me how fast they can be :-O</p>
]]></content:encoded>
	</item>
</channel>
</rss>

