<?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: 1.5 to 2.0 transactions a second? Try XFire</title>
	<atom:link href="http://netzooid.com/blog/2005/10/31/15-to-20-transactions-a-second-try-xfire/feed/" rel="self" type="application/rss+xml" />
	<link>http://netzooid.com/blog/2005/10/31/15-to-20-transactions-a-second-try-xfire/</link>
	<description>gettin all zoidal on ya</description>
	<lastBuildDate>Sat, 24 Jul 2010 09:48:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: netzooid &#187; More Notes on SOAP and XFire Performance</title>
		<link>http://netzooid.com/blog/2005/10/31/15-to-20-transactions-a-second-try-xfire/comment-page-1/#comment-186</link>
		<dc:creator>netzooid &#187; More Notes on SOAP and XFire Performance</dc:creator>
		<pubDate>Thu, 03 Nov 2005 18:55:23 +0000</pubDate>
		<guid isPermaLink="false">http://netzooid.com/blog/?p=108#comment-186</guid>
		<description>[...] I ran across this entry on XFire performance from Tim Pokorny by accident yesterday. While I feel my numbers speak for themselves, its always good to hear it from a user: ...I decided to run only one client for 60 seconds and only on the AMD. It was able to get 3919 iterations completed in those 60 seconds. That is more than 65 updates per second. Perhaps the most amazing thing about this is the actual performance of web services (XFire in this case). These were not small updates either; two entities, each with something like eight attributes were being serialised into XML, sent over the wire and de-serialised into Java objects 65 times per second! That is HUGE. To put this in perspective, when previously asked by people about the real performance of web services (in the simulation context) I estimated that I could consistently get about 8 updates a second. Needless to say, 65 is almost an order of magnitude faster than that. [...]</description>
		<content:encoded><![CDATA[<p>[...] I ran across this entry on XFire performance from Tim Pokorny by accident yesterday. While I feel my numbers speak for themselves, its always good to hear it from a user: &#8230;I decided to run only one client for 60 seconds and only on the AMD. It was able to get 3919 iterations completed in those 60 seconds. That is more than 65 updates per second. Perhaps the most amazing thing about this is the actual performance of web services (XFire in this case). These were not small updates either; two entities, each with something like eight attributes were being serialised into XML, sent over the wire and de-serialised into Java objects 65 times per second! That is HUGE. To put this in perspective, when previously asked by people about the real performance of web services (in the simulation context) I estimated that I could consistently get about 8 updates a second. Needless to say, 65 is almost an order of magnitude faster than that. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
