<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://azeemjiva.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Azeem Jiva</title>
 <link>http://azeemjiva.sys-con.com/</link>
 <description>Latest News from Azeem Jiva</description>
 <language>en</language>
 <copyright>Copyright 2012 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Wed, 16 May 2012 10:38:03 EDT</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Multi-Core Event Based Profiling</title>
 <link>http://azeemjiva.sys-con.com/node/1034450</link>
 <description>In this article, we will use a sample application to demonstrate how CodeAnalyst can profile your Java application. You will learn how to setup a CodeAnalyst project to use Event Based Profiling to get an idea of what to investigate in your own Java applications. Event-Based Profiling allows the developer to tie in running code with hardware events such as a cache miss, locked instructions or pipeline stalls. If you are new to CodeAnalyst, please see Using AMD CodeAnalyst with Java.&lt;p&gt;&lt;a href=&quot;http://azeemjiva.sys-con.com/node/1034450&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 31 Dec 1969 19:00:00 EST</pubDate>
 <guid isPermaLink="true">http://azeemjiva.sys-con.com/node/1034450</guid>
 <comments>http://azeemjiva.sys-con.com/node/1034450#feedback</comments>
</item>
</channel>
</rss>

