<?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: Monitoring Rails: Getting instant monitoring alerts</title>
	<atom:link href="http://www.coffeepowered.net/2009/03/13/monitoring-rails-getting-instant-monitoring-alerts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.coffeepowered.net/2009/03/13/monitoring-rails-getting-instant-monitoring-alerts/</link>
	<description>code and content</description>
	<lastBuildDate>Tue, 24 Aug 2010 01:23:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Chris Heald</title>
		<link>http://www.coffeepowered.net/2009/03/13/monitoring-rails-getting-instant-monitoring-alerts/comment-page-1/#comment-164</link>
		<dc:creator>Chris Heald</dc:creator>
		<pubDate>Tue, 17 Mar 2009 12:06:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.coffeepowered.net/?p=145#comment-164</guid>
		<description>I haven&#039;t run into an upper limit yet, even when I managed to introduce an errant logging mechanism into my code that caused me to send about 80,000 messages in 60 seconds, heh. 
 
It would be fairly easy to cut out the DRb piece if it became a limiting factor - using an eventmachine daemon rather than a DRb daemon would be relatively easy, though not quite as brainlessly easy as using DRb. </description>
		<content:encoded><![CDATA[<p>I haven&#039;t run into an upper limit yet, even when I managed to introduce an errant logging mechanism into my code that caused me to send about 80,000 messages in 60 seconds, heh.</p>
<p>It would be fairly easy to cut out the DRb piece if it became a limiting factor &#8211; using an eventmachine daemon rather than a DRb daemon would be relatively easy, though not quite as brainlessly easy as using DRb.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julien</title>
		<link>http://www.coffeepowered.net/2009/03/13/monitoring-rails-getting-instant-monitoring-alerts/comment-page-1/#comment-163</link>
		<dc:creator>Julien</dc:creator>
		<pubDate>Tue, 17 Mar 2009 10:17:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.coffeepowered.net/?p=145#comment-163</guid>
		<description>I might try do do it myself ;) 
 
Anyway, I see that you use Drb for communication between your mongrels and the XMPP process. How &quot;scalable&quot; is that? 
 
I mean, can you give us some hints on performance? </description>
		<content:encoded><![CDATA[<p>I might try do do it myself ;)</p>
<p>Anyway, I see that you use Drb for communication between your mongrels and the XMPP process. How &quot;scalable&quot; is that?</p>
<p>I mean, can you give us some hints on performance?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Heald</title>
		<link>http://www.coffeepowered.net/2009/03/13/monitoring-rails-getting-instant-monitoring-alerts/comment-page-1/#comment-150</link>
		<dc:creator>Chris Heald</dc:creator>
		<pubDate>Fri, 13 Mar 2009 12:56:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.coffeepowered.net/?p=145#comment-150</guid>
		<description>Very interesting work there. I can&#039;t say I&#039;ve needed super high-performance XMPP in Rails yet, but having the option is always very good. Jabberish could very easily be wrapped around Babylon - it&#039;s really just a mechanism to abstract the actual XMPP setup away from the user, so they just write messages to it and don&#039;t worry about concurrency and the like. 
 
I&#039;ll see about Babylon support! </description>
		<content:encoded><![CDATA[<p>Very interesting work there. I can&#039;t say I&#039;ve needed super high-performance XMPP in Rails yet, but having the option is always very good. Jabberish could very easily be wrapped around Babylon &#8211; it&#039;s really just a mechanism to abstract the actual XMPP setup away from the user, so they just write messages to it and don&#039;t worry about concurrency and the like.</p>
<p>I&#039;ll see about Babylon support!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julien</title>
		<link>http://www.coffeepowered.net/2009/03/13/monitoring-rails-getting-instant-monitoring-alerts/comment-page-1/#comment-149</link>
		<dc:creator>Julien</dc:creator>
		<pubDate>Fri, 13 Mar 2009 08:41:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.coffeepowered.net/?p=145#comment-149</guid>
		<description>Hey,  
 
I think Jabberrish is a great idea! And I would really love to see more mixed XMPP adn HTTP apps... but, honestly, XMPP4R (and its threaded architecture) really can&#039;t handle the load of thousands of messages per minute! I am working on a project that hopes to make XMPP better for Ruby : &lt;a href=&quot;http://github.com/julien51/babylon/tree/master&quot; rel=&quot;nofollow&quot;&gt;http://github.com/julien51/babylon/tree/master&lt;/a&gt;  
 
Do you think you could &quot;port&quot; Jabberrish to use it? </description>
		<content:encoded><![CDATA[<p>Hey, </p>
<p>I think Jabberrish is a great idea! And I would really love to see more mixed XMPP adn HTTP apps&#8230; but, honestly, XMPP4R (and its threaded architecture) really can&#039;t handle the load of thousands of messages per minute! I am working on a project that hopes to make XMPP better for Ruby : <a href="http://github.com/julien51/babylon/tree/master" rel="nofollow">http://github.com/julien51/babylon/tree/master</a>  </p>
<p>Do you think you could &quot;port&quot; Jabberrish to use it?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using memcached
Page Caching using memcached
Database Caching 9/18 queries in 0.009 seconds using memcached

Served from: www.coffeepowered.net @ 2010-09-07 07:22:25 -->