<?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: How Rapid is Rapid? How Quick is Quick?</title>
	<atom:link href="http://rocksolid.gibraltarsoftware.com/development/logging/how-rapid-is-rapid-how-quick-is-quick/feed" rel="self" type="application/rss+xml" />
	<link>http://rocksolid.gibraltarsoftware.com/development/logging/how-rapid-is-rapid-how-quick-is-quick</link>
	<description>Notes from the folks behind Gibraltar Software</description>
	<lastBuildDate>Sat, 10 Dec 2011 21:22:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: jay</title>
		<link>http://rocksolid.gibraltarsoftware.com/development/logging/how-rapid-is-rapid-how-quick-is-quick/comment-page-1#comment-11</link>
		<dc:creator>jay</dc:creator>
		<pubDate>Wed, 13 May 2009 22:42:37 +0000</pubDate>
		<guid isPermaLink="false">http://rocksolid.gibraltarsoftware.com/?p=13#comment-11</guid>
		<description>The calculation of 6000 msgs/sec was based on extremely simplistic code that opened/closed a file for each message.  By simply keeping the file open Kendall showed that the speed could easily be increased 24x to 142,000 msgs/sec.

His point was that, for most systems, an average load of even 6000 msg/second is way more than needed.

A second important point that was not discussed in the article is that even if the logging rate is slow, NotePad or it&#039;s ilk become utterly useless for making sense out of log data.

This is why our product, Gibraltar, has great mechanisms for searching, filtering and highlighting log messages as well as graphing related metrics.  We also analyze data across multiple logs.

More info on Gibraltar and a free trial is available at www.GibraltarSoftware.com</description>
		<content:encoded><![CDATA[<p>The calculation of 6000 msgs/sec was based on extremely simplistic code that opened/closed a file for each message.  By simply keeping the file open Kendall showed that the speed could easily be increased 24x to 142,000 msgs/sec.</p>
<p>His point was that, for most systems, an average load of even 6000 msg/second is way more than needed.</p>
<p>A second important point that was not discussed in the article is that even if the logging rate is slow, NotePad or it&#8217;s ilk become utterly useless for making sense out of log data.</p>
<p>This is why our product, Gibraltar, has great mechanisms for searching, filtering and highlighting log messages as well as graphing related metrics.  We also analyze data across multiple logs.</p>
<p>More info on Gibraltar and a free trial is available at <a href="http://www.GibraltarSoftware.com" rel="nofollow">http://www.GibraltarSoftware.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pave</title>
		<link>http://rocksolid.gibraltarsoftware.com/development/logging/how-rapid-is-rapid-how-quick-is-quick/comment-page-1#comment-10</link>
		<dc:creator>Pave</dc:creator>
		<pubDate>Wed, 13 May 2009 19:18:18 +0000</pubDate>
		<guid isPermaLink="false">http://rocksolid.gibraltarsoftware.com/?p=13#comment-10</guid>
		<description>Hey Kendall, pretty cool article, and also got me thinking.
I have developed a custom logging system for my project, and it takes speed into very serious consideration, you can check it out, its open source at www.openforexplatform.com

However my point is 6,000 messages per second is not so much at all, the system I mentioned does a few times that under *medium* load. Now if you use a Notepad to look trough your traces, this amount will most certainly be utterly useless, that is why I developed a sophisticated UI control to go with the logging system. It allows searching, filtering by class, by type, by importance etc.

So now ever though I have 150,000+ items in my list view, I can very promptly find anything I need inside it (most often errors, warnings etc.)</description>
		<content:encoded><![CDATA[<p>Hey Kendall, pretty cool article, and also got me thinking.<br />
I have developed a custom logging system for my project, and it takes speed into very serious consideration, you can check it out, its open source at <a href="http://www.openforexplatform.com" rel="nofollow">http://www.openforexplatform.com</a></p>
<p>However my point is 6,000 messages per second is not so much at all, the system I mentioned does a few times that under *medium* load. Now if you use a Notepad to look trough your traces, this amount will most certainly be utterly useless, that is why I developed a sophisticated UI control to go with the logging system. It allows searching, filtering by class, by type, by importance etc.</p>
<p>So now ever though I have 150,000+ items in my list view, I can very promptly find anything I need inside it (most often errors, warnings etc.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

