﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on NH Prof: Getting big, and bigger</title><description>Unfortunately, I actually do need to process all / most of them.
  
The SQL Formatter part is also responsible for creating the nice listing in the headers, which is almost always needed anyway
</description><link>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment8</link><guid>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment8</guid><pubDate>Fri, 26 Jun 2009 05:52:17 GMT</pubDate></item><item><title>Fabio Maulo commented on NH Prof: Getting big, and bigger</title><description>If you think that the SQL formatting is a possible point to improve performances perhaps you should move it up, if the SQL formatting is really only to show a fashion SQL to the user.
</description><link>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment7</link><guid>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment7</guid><pubDate>Fri, 26 Jun 2009 05:46:09 GMT</pubDate></item><item><title>Ayende Rahien commented on NH Prof: Getting big, and bigger</title><description>Fabio,
  
This is done on the backend portion of NH Prof
</description><link>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment6</link><guid>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment6</guid><pubDate>Fri, 26 Jun 2009 05:36:04 GMT</pubDate></item><item><title>Fabio Maulo commented on NH Prof: Getting big, and bigger</title><description>The "format the SQL" is a responsibility of which tear of NHProf ?
</description><link>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment5</link><guid>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment5</guid><pubDate>Fri, 26 Jun 2009 03:59:35 GMT</pubDate></item><item><title>Ayende Rahien commented on NH Prof: Getting big, and bigger</title><description>Thomas,
  
No, processing events is done in a single background thread, that significantly simplify what I need to do to bring it all into a single cohesive model.
</description><link>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment4</link><guid>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment4</guid><pubDate>Thu, 25 Jun 2009 13:40:39 GMT</pubDate></item><item><title>Thomas Krause commented on NH Prof: Getting big, and bigger</title><description>How well does the performance scale with the number of cpu cores?
  
  
Do you use multi threading at all for processing the events and if yes how do you partition the work between multiple threads?
</description><link>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment3</link><guid>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment3</guid><pubDate>Thu, 25 Jun 2009 13:12:23 GMT</pubDate></item><item><title>Ayende Rahien commented on NH Prof: Getting big, and bigger</title><description>Rafal,
  
No, it is an in memory queue.
  
And it is actually about the processing time &amp; IO than anything related to the queue.
  
In memory queue, naively implemented, can easily do millions per second.
  
  
I intent to sit on the RQ perf issue when I have free time, mind you.
</description><link>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment2</link><guid>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment2</guid><pubDate>Thu, 25 Jun 2009 08:01:31 GMT</pubDate></item><item><title>Rafal commented on NH Prof: Getting big, and bigger</title><description>Over 2000 events per second? Impressive, is your queue running on Rhino Queues or sth else? (I'm asking because some time ago I had problems with RQ performance, it was nowhere near 2000 messages/second)
</description><link>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment1</link><guid>http://ayende.com/4062/nh-prof-getting-big-and-bigger#comment1</guid><pubDate>Thu, 25 Jun 2009 07:55:26 GMT</pubDate></item></channel></rss>