<?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>Xebia Blog &#187; Performance</title>
	<atom:link href="http://blog.xebia.com/category/performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.xebia.com</link>
	<description></description>
	<lastBuildDate>Wed, 28 Jul 2010 13:11:22 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Web performance in seven steps: Summary and Conclusions</title>
		<link>http://blog.xebia.com/2010/01/20/web-performance-in-seven-steps-summery-and-conclusions/</link>
		<comments>http://blog.xebia.com/2010/01/20/web-performance-in-seven-steps-summery-and-conclusions/#comments</comments>
		<pubDate>Wed, 20 Jan 2010 20:00:22 +0000</pubDate>
		<dc:creator>Jeroen Borgers</dc:creator>
		<br />
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/blog.xebia.com/www/wp-content/plugins/autometa/autometa.php</b> on line <b>303</b><br />
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Monitoring]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Quality Assurance]]></category>
		<category><![CDATA[Requirements Management]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[Tools]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=3962</guid>
		<description><![CDATA[Previous time I blogged about the last step of the seven steps, step 7: Share the responsibility for the whole chain, a non-technical but rather a communication and behavior thing which I found crucial for success. We now have reached the end of this series and I'll sum up the topics we've dealt with and [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2010/01/20/web-performance-in-seven-steps-summery-and-conclusions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Web performance in seven steps; Step 7: Share the responsibility for the whole chain</title>
		<link>http://blog.xebia.com/2009/11/18/web-performance-in-seven-steps-step-7-share-the-responsibility-for-the-whole-chain/</link>
		<comments>http://blog.xebia.com/2009/11/18/web-performance-in-seven-steps-step-7-share-the-responsibility-for-the-whole-chain/#comments</comments>
		<pubDate>Wed, 18 Nov 2009 21:20:15 +0000</pubDate>
		<dc:creator>Jeroen Borgers</dc:creator>
		<br />
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/blog.xebia.com/www/wp-content/plugins/autometa/autometa.php</b> on line <b>303</b><br />
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Tools]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=3537</guid>
		<description><![CDATA[Last time I blogged about performance tuning based on evidence, the tuning cycle and some best practices. This time I'll blog about the last step of the seven steps: sharing the responsibility for the whole system chain.
When an incident happens in production, this usually means stress. A performance problem in production often leads to finger [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2009/11/18/web-performance-in-seven-steps-step-7-share-the-responsibility-for-the-whole-chain/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Web performance in seven steps; Step 6: Tune based on evidence</title>
		<link>http://blog.xebia.com/2009/11/02/web-performance-in-seven-steps-step-6-tune-based-on-evidence/</link>
		<comments>http://blog.xebia.com/2009/11/02/web-performance-in-seven-steps-step-6-tune-based-on-evidence/#comments</comments>
		<pubDate>Mon, 02 Nov 2009 21:20:11 +0000</pubDate>
		<dc:creator>Jeroen Borgers</dc:creator>
		<br />
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/blog.xebia.com/www/wp-content/plugins/autometa/autometa.php</b> on line <b>303</b><br />
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[tuning]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=3376</guid>
		<description><![CDATA[Last time I blogged about the relevance of monitoring and diagnostics in production to solve incidents quickly and prevent future problems. This time I'll talk about tuning based on evidence. 
If an application turns out to be too slow, tuning can provide a solution. Tuning can take place on multiple levels. Adding hardware can be [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2009/11/02/web-performance-in-seven-steps-step-6-tune-based-on-evidence/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Web performance in seven steps; Step 5: Monitor and diagnose</title>
		<link>http://blog.xebia.com/2009/08/31/web-performance-in-seven-steps-step-5-monitor-and-diagnose/</link>
		<comments>http://blog.xebia.com/2009/08/31/web-performance-in-seven-steps-step-5-monitor-and-diagnose/#comments</comments>
		<pubDate>Mon, 31 Aug 2009 22:38:36 +0000</pubDate>
		<dc:creator>Jeroen Borgers</dc:creator>
		<br />
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/blog.xebia.com/www/wp-content/plugins/autometa/autometa.php</b> on line <b>303</b><br />
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Monitoring]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[JAMon]]></category>
		<category><![CDATA[JARep]]></category>
		<category><![CDATA[Opensource]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=3076</guid>
		<description><![CDATA[Last time I blogged about the importance of continuous performance testing. When you write and run performance tests continuously, just like unit tests, you get early performance insights in new and changed features of your software. This will minimize surprises and be more productive. Now I’ll blog about monitoring and diagnostics.
When a new version of [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2009/08/31/web-performance-in-seven-steps-step-5-monitor-and-diagnose/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Web performance in seven steps; Step 4: Test continuously</title>
		<link>http://blog.xebia.com/2009/07/22/web-performance-in-seven-steps-step-4-test-continuously/</link>
		<comments>http://blog.xebia.com/2009/07/22/web-performance-in-seven-steps-step-4-test-continuously/#comments</comments>
		<pubDate>Wed, 22 Jul 2009 20:25:17 +0000</pubDate>
		<dc:creator>Jeroen Borgers</dc:creator>
		<br />
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/blog.xebia.com/www/wp-content/plugins/autometa/autometa.php</b> on line <b>303</b><br />
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Quality Assurance]]></category>
		<category><![CDATA[Testing]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=2694</guid>
		<description><![CDATA[Last time I blogged about the importance of representative performance testing. Having production-like properties for hardware, OS, JVM, app server, database, external systems and simulated user load are essential to prevent bad performance surprises when going live. In addition, I described how cloud computing can be utilized to generate high loads on-demand without having to [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2009/07/22/web-performance-in-seven-steps-step-4-test-continuously/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Web performance in seven steps; step 3: test representatively</title>
		<link>http://blog.xebia.com/2009/06/29/web-performance-in-seven-steps-step-3-test-representatively/</link>
		<comments>http://blog.xebia.com/2009/06/29/web-performance-in-seven-steps-step-3-test-representatively/#comments</comments>
		<pubDate>Mon, 29 Jun 2009 20:34:44 +0000</pubDate>
		<dc:creator>Jeroen Borgers</dc:creator>
		<br />
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/blog.xebia.com/www/wp-content/plugins/autometa/autometa.php</b> on line <b>303</b><br />
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Quality Assurance]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[JMeter]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=2269</guid>
		<description><![CDATA[Last time I blogged about the importance of benchmarking the architecture and new technology in a Proof of Concept for Performance. This time I’ll deal with the importance of representative performance testing. 
Slowness of applications in development environments is often neglected with the rationale that faster hardware in the production environment will solve this problem. [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2009/06/29/web-performance-in-seven-steps-step-3-test-representatively/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Web performance in seven steps; step 2: Execute a proof of concept</title>
		<link>http://blog.xebia.com/2009/06/15/web-performance-in-seven-steps-step-2-execute-a-proof-of-concept/</link>
		<comments>http://blog.xebia.com/2009/06/15/web-performance-in-seven-steps-step-2-execute-a-proof-of-concept/#comments</comments>
		<pubDate>Mon, 15 Jun 2009 19:40:14 +0000</pubDate>
		<dc:creator>Jeroen Borgers</dc:creator>
		<br />
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/blog.xebia.com/www/wp-content/plugins/autometa/autometa.php</b> on line <b>303</b><br />
		<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Quality Assurance]]></category>
		<category><![CDATA[Requirements Management]]></category>
		<category><![CDATA[Testing]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=2036</guid>
		<description><![CDATA[Last week I blogged about setting your performance goals: defining your requirements. This time I'll blog about the importance of a Proof of Concept for performance.
The IT world is very sensitive to trends. Having been around in the IT industry for 15 years, I’ve seen a few. A technology is hot for a while, and [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2009/06/15/web-performance-in-seven-steps-step-2-execute-a-proof-of-concept/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JPA implementation patterns: Field access vs. property access</title>
		<link>http://blog.xebia.com/2009/06/13/jpa-implementation-patterns-field-access-vs-property-access/</link>
		<comments>http://blog.xebia.com/2009/06/13/jpa-implementation-patterns-field-access-vs-property-access/#comments</comments>
		<pubDate>Sat, 13 Jun 2009 11:14:18 +0000</pubDate>
		<dc:creator>Vincent Partington</dc:creator>
		<br />
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/blog.xebia.com/www/wp-content/plugins/autometa/autometa.php</b> on line <b>303</b><br />
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Hibernate]]></category>
		<category><![CDATA[JPA]]></category>
		<category><![CDATA[JPA implementation patterns]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=2007</guid>
		<description><![CDATA[Last week my colleague Albert Sikkema blogged about using UUIDs as primary keys. Interesting stuff, thanks again, Albert! This week I will continue the JPA implementation patterns series by discussing the relative merits of field access vs. property access.
 The JPA specification allows two ways for the persistence provider to access the persistent state of [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2009/06/13/jpa-implementation-patterns-field-access-vs-property-access/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Web performance in seven steps; step 1: define performance requirements</title>
		<link>http://blog.xebia.com/2009/06/10/web-performance-in-seven-steps-step-1-define-performance-requirements/</link>
		<comments>http://blog.xebia.com/2009/06/10/web-performance-in-seven-steps-step-1-define-performance-requirements/#comments</comments>
		<pubDate>Wed, 10 Jun 2009 20:33:27 +0000</pubDate>
		<dc:creator>Jeroen Borgers</dc:creator>
		<br />
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/blog.xebia.com/www/wp-content/plugins/autometa/autometa.php</b> on line <b>303</b><br />
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Requirements Management]]></category>
		<category><![CDATA[requirements]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=1990</guid>
		<description><![CDATA[Last week I blogged about how performance problems manifest themselves: frustration, loss of revenue and disruption of development; and how adding hardware is a questionable solution. This week I'll blog about the first step to assure web performance.
It can be a valid choice to run the risk of performance problems in production and deal with [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2009/06/10/web-performance-in-seven-steps-step-1-define-performance-requirements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Web performance in seven steps; how performance problems manifest themselves</title>
		<link>http://blog.xebia.com/2009/06/02/web-performance-in-seven-steps-how-performance-problems-manifest-themselves/</link>
		<comments>http://blog.xebia.com/2009/06/02/web-performance-in-seven-steps-how-performance-problems-manifest-themselves/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 19:33:55 +0000</pubDate>
		<dc:creator>Jeroen Borgers</dc:creator>
		<br />
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/blog.xebia.com/www/wp-content/plugins/autometa/autometa.php</b> on line <b>303</b><br />
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Performance]]></category>
		<category><![CDATA[Quality Assurance]]></category>
		<category><![CDATA[availability]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[frustration]]></category>
		<category><![CDATA[hardware]]></category>
		<category><![CDATA[load]]></category>
		<category><![CDATA[speed.]]></category>
		<category><![CDATA[troubleshooting]]></category>
		<category><![CDATA[web shop]]></category>

	<!-- AutoMeta Start -->
	<!-- AutoMeta End -->
	
		<guid isPermaLink="false">http://blog.xebia.com/?p=1873</guid>
		<description><![CDATA[Last week I blogged about the increasing load at web shops and the increasing challenges for developers and operators. The question to be answered was stated as: how can we prevent performance and availability problems; how can we assure that a web site is always quick and available? In this blog I’ll describe some of [...]]]></description>
		<wfw:commentRss>http://blog.xebia.com/2009/06/02/web-performance-in-seven-steps-how-performance-problems-manifest-themselves/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
