<?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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Blog O' Matty &#187; Solaris DTrace</title>
	<atom:link href="http://prefetch.net/blog/index.php/category/solaris-dtrace/feed/" rel="self" type="application/rss+xml" />
	<link>http://prefetch.net/blog</link>
	<description>Blog O' Matty</description>
	<lastBuildDate>Tue, 07 Feb 2012 03:00:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Using Solaris source code + DTrace</title>
		<link>http://prefetch.net/blog/index.php/2009/10/31/using-solaris-source-code-dtrace/</link>
		<comments>http://prefetch.net/blog/index.php/2009/10/31/using-solaris-source-code-dtrace/#comments</comments>
		<pubDate>Sat, 31 Oct 2009 13:54:18 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Solaris DTrace]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/?p=3056</guid>
		<description><![CDATA[Brian Leonard wrote an excellent blog post about how to use DTrace, how to show details about specific probes, and then using the source code in conjunction with his findings to understand exactly what was happening within that probe.  if you&#8217;re starting to deep dive into DTrace, this is an excellent article for learning these [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2009/10/31/using-solaris-source-code-dtrace/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Instrumenting Java code with  JSDT probes</title>
		<link>http://prefetch.net/blog/index.php/2009/04/08/instrumenting-java-code-with-jsdt-probes/</link>
		<comments>http://prefetch.net/blog/index.php/2009/04/08/instrumenting-java-code-with-jsdt-probes/#comments</comments>
		<pubDate>Wed, 08 Apr 2009 17:33:59 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Solaris DTrace]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/?p=1379</guid>
		<description><![CDATA[A few months back, I got wind from the world famous Jarod Jenson that Keith McGuigan was working on adding JSDT probes to Java. JSDT probes struck me as an extremely useful feature for realtime problem analysis, so I decided to instrument some sample code to see how they worked. After a couple of e-mail [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2009/04/08/instrumenting-java-code-with-jsdt-probes/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Using the DTrace hotspot provider to observe java object allocations</title>
		<link>http://prefetch.net/blog/index.php/2007/10/31/using-the-dtrace-hotspot-provider-to-observe-java-object-allocations/</link>
		<comments>http://prefetch.net/blog/index.php/2007/10/31/using-the-dtrace-hotspot-provider-to-observe-java-object-allocations/#comments</comments>
		<pubDate>Thu, 01 Nov 2007 02:48:51 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Solaris DTrace]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/10/31/using-the-dtrace-hotspot-provider-to-observe-java-object-allocations/</guid>
		<description><![CDATA[In my previous post, I discussed how jmap can be used to view the contents of the Java heap. Jmap is a wonderful utility for viewing heap utilization at a specific point in time, but it&#8217;s not the best utiltiy for answer questions like &#8220;which call stack is allocating objects of type foo?&#8221;, or &#8220;how [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2007/10/31/using-the-dtrace-hotspot-provider-to-observe-java-object-allocations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Enabling the DTrace hotspot provider after the JVM starts</title>
		<link>http://prefetch.net/blog/index.php/2007/10/18/enabling-the-dtrace-hotspot-provider-after-the-jvm-starts/</link>
		<comments>http://prefetch.net/blog/index.php/2007/10/18/enabling-the-dtrace-hotspot-provider-after-the-jvm-starts/#comments</comments>
		<pubDate>Thu, 18 Oct 2007 04:40:04 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Solaris DTrace]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/10/18/enabling-the-dtrace-hotspot-provider-after-the-jvm-starts/</guid>
		<description><![CDATA[While debugging a JVM performance issue a while back, I encountered the following error when I enabled the DTrace hotspot provider: $ jinfo -flag +ExtendedDTraceProbes `pgrep java` 590: Unable to open door: target process not responding or HotSpot VM not loaded After a bit of debugging, I figured out that the jinfo command needs to [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2007/10/18/enabling-the-dtrace-hotspot-provider-after-the-jvm-starts/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Measuring system call time with procsystime</title>
		<link>http://prefetch.net/blog/index.php/2007/03/17/measuring-system-call-time-with-procsystime/</link>
		<comments>http://prefetch.net/blog/index.php/2007/03/17/measuring-system-call-time-with-procsystime/#comments</comments>
		<pubDate>Sat, 17 Mar 2007 14:47:45 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Solaris DTrace]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/03/17/measuring-system-call-time-with-procsystime/</guid>
		<description><![CDATA[When debugging application performance problems related to high system time, I typically start my analysis by watching the system calls the application is issuing, and measuring how much time is spent in each system call. Gathering this information is simple with DTrace syscall provider, and the DTraceToolkit comes with the procsystime script to allow admins [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2007/03/17/measuring-system-call-time-with-procsystime/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Viewing busy code paths with DTrace</title>
		<link>http://prefetch.net/blog/index.php/2007/03/03/viewing-busy-code-paths-with-dtrace/</link>
		<comments>http://prefetch.net/blog/index.php/2007/03/03/viewing-busy-code-paths-with-dtrace/#comments</comments>
		<pubDate>Sat, 03 Mar 2007 15:14:01 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Solaris DTrace]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/03/03/viewing-busy-code-paths-with-dtrace/</guid>
		<description><![CDATA[Periodically I want to see the busiest application and system code paths on a system. Prior to Solaris 10, this was a difficult questions to answer without custom instrumentation. Now that we have DTrace, we can use the DTrace profile provider and an aggregation to view the busiest code paths in the kernel: $ dtrace [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2007/03/03/viewing-busy-code-paths-with-dtrace/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Debugging directory server issues with DTrace</title>
		<link>http://prefetch.net/blog/index.php/2007/01/17/debugging-directory-server-issues-with-dtrace/</link>
		<comments>http://prefetch.net/blog/index.php/2007/01/17/debugging-directory-server-issues-with-dtrace/#comments</comments>
		<pubDate>Wed, 17 Jan 2007 23:48:57 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Solaris DTrace]]></category>
		<category><![CDATA[Sun Directory Server]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2007/01/17/debugging-directory-server-issues-with-dtrace/</guid>
		<description><![CDATA[Today while installing Sun&#8217;s directory server, I kept getting the error &#8220;No components have been selected for installation in the selected directory&#8221; after selecting numerous components for installation: Directory Server components showing a checked box will be installed. [X] 1 Sun Java(TM) System Directory Suite 0 bytes [X] 2 Sun Java(TM) System Directory Server 0 [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2007/01/17/debugging-directory-server-issues-with-dtrace/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Viewing utilization per file descriptor on Solaris 10 hosts</title>
		<link>http://prefetch.net/blog/index.php/2006/11/10/viewing-utilization-per-file-descriptor/</link>
		<comments>http://prefetch.net/blog/index.php/2006/11/10/viewing-utilization-per-file-descriptor/#comments</comments>
		<pubDate>Fri, 10 Nov 2006 23:08:26 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Solaris DTrace]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2006/11/10/viewing-utilization-per-file-descriptor/</guid>
		<description><![CDATA[While load-testing a MySQL back-end last weekend, I wanted to be able to monitor read and write utilization per file descriptor. The DTraceToolkit comes with a nifty script named pfilestat that does just that: $ pfilestat 841 STATE FDNUM Time Filename read 63 0% /tmp/#sql_349_0.MYI write 64 0% /tmp/#sql_349_0.MYD read 64 0% /tmp/#sql_349_0.MYD write 63 [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2006/11/10/viewing-utilization-per-file-descriptor/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Brendan Gregg amazes me again</title>
		<link>http://prefetch.net/blog/index.php/2006/09/20/brendan-gregg-amazes-me-again/</link>
		<comments>http://prefetch.net/blog/index.php/2006/09/20/brendan-gregg-amazes-me-again/#comments</comments>
		<pubDate>Wed, 20 Sep 2006 21:20:26 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Solaris DTrace]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2006/09/20/brendan-gregg-amazes-me-again/</guid>
		<description><![CDATA[I spent some time last night catching up with mailing lists, and saw that Brendan Gregg recently added DTrace SDT probes to one of the Javascript engines. If you don&#8217;t know who Brendan is, he is a brilliant guy, and the author of the DTraceToolkit among other things. I always love reading about his work, [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2006/09/20/brendan-gregg-amazes-me-again/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Determining if an application is using random vs. sequential I/O</title>
		<link>http://prefetch.net/blog/index.php/2006/09/13/determining-if-an-application-is-using-random-vs-sequential-io/</link>
		<comments>http://prefetch.net/blog/index.php/2006/09/13/determining-if-an-application-is-using-random-vs-sequential-io/#comments</comments>
		<pubDate>Wed, 13 Sep 2006 19:09:37 +0000</pubDate>
		<dc:creator>matty</dc:creator>
				<category><![CDATA[Solaris DTrace]]></category>

		<guid isPermaLink="false">http://prefetch.net/blog/index.php/2006/09/13/determining-if-an-application-is-using-random-vs-sequential-io/</guid>
		<description><![CDATA[The DTraceToolkit comes with two super useful scripts to observe the &#8220;randonmess&#8221; or &#8220;sequentialness&#8221; of an application. The first script is iopattern, which provides a system-wide view of random and sequential I/O, the total amount of I/O generated, and an I/O size distribution: $ iopattern 5 %RAN %SEQ COUNT MIN MAX AVG KR KW 100 [...]]]></description>
		<wfw:commentRss>http://prefetch.net/blog/index.php/2006/09/13/determining-if-an-application-is-using-random-vs-sequential-io/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

