On Sun, Mar 22, 2009 at 4:45 AM, ecin <e...@copypastel.com> wrote:
>
> For this years Google Summer of Code, I want to implement a set of
> Dtrace [1] probes in Rack [2]. The idea is to create a profiling tool
> that easily works across a number of Ruby web-frameworks and web-
> servers and provide insight into a web-app's performance.
> Node monitoring and management are within the problem domain as well.
>
> The Dtrace probes can be coded into a Rack module using ruby-dtrace
> [3]. This means that adding a useful set of profiling statistics to
> any web-app would be as easy as uncommenting an 'autoload' line.
>
> I posted this information on Rack's mailing list [4] as well, and
> learned about Orchestra [5] and Rack::Bug [6] as a result. While
> Orchestra aims to do what I propose in a platform-agnostic way,
> Rack::Bug could better be described as a front-end to the information
> produced. These are projects I can lean on and work with during the
> summer. Orchestra provides a messaging system to facilitate the usage
> of the information produced by probes and Rack::Bug serves as a
> testbed consumer for the same information.
>
> Any suggestions or comments on this idea?

I think this is a great idea that benefits all Rails and Rack apps,
ecin. Is it a whole summer's work, though? What kind of probes would
you provide?

Perhaps you could provide some tooling support as well to make
answering common Rails/Rack performance questions easy.

What are the concrete goals you'd hope to achieve by the end of the summer?

Best,
jeremy

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To post to this group, send email to rubyonrails-core@googlegroups.com
To unsubscribe from this group, send email to 
rubyonrails-core+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to