<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://changhaohuang.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Huang Chang Hao</title>
 <link>http://changhaohuang.sys-con.com/</link>
 <description>Latest News from Huang Chang Hao</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Tue, 01 Dec 2009 00:54:02 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>A Study of XPath Performance in .NET Programming</title>
 <link>http://changhaohuang.sys-con.com/node/792866</link>
 <description>One day, I received an e-mail from a customer complaining that there was 100% CPU occupancy on our program, EDC (Engineering Data Collection) service, while handling certain XPath queries. I decided to do some tests on the program and some other alternative solutions. I set two goals for this test: to verify if the XML parser is the part causing 100% CPU usage; if so, to try to find alternative solutions for better performance.&lt;p&gt;&lt;a href=&quot;http://changhaohuang.sys-con.com/node/792866&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 02 Jan 2009 07:15:00 EST</pubDate>
 <guid isPermaLink="true">http://changhaohuang.sys-con.com/node/792866</guid>
 <comments>http://changhaohuang.sys-con.com/node/792866#feedback</comments>
</item>
</channel>
</rss>
