RubyRunCE

Scenario 1: Continuous awareness, from the top down
Manager A needs a performance summary report
every hour straight to his desktop computer. His team is
responsible for ensuring that one of the company's most
important mission-critical applications meets certain response times ... all the time. So, the
Throughput and Top 10 slowest request graphs are very valuable to him. Hourly RubyRunCE diagnostic reports keep him informed - before a molehill grows into a mountain.

Scenario 2: Quickly determine the root cause
On a deeper level, diagnostic engineers need
to see what is causing a request to hang or take excessive time to
complete. RubyRunCE reports allow engineers to quickly determine the type of
problem in progress, easily allowing them to determine the
right engineer to deploy. For example, high database I/O
times may indicate that it's time to contact the database
administrator and ask her to run some diagnostics, or a long
dispatch delay may suggest that more Mongrel servers are
needed to cope with the volume of throughput. RubyRunCE
provides "x-ray vision" into your application.

Scenario 3: A magnifying glass for developers
Here's a common problem: A developer wants to
find delay hotspots without guessing: inefficient classes or
methods that were integrated from other developers' code and
third-party components. RubyRunCE diagnostics reports allows the developer to view a complete code flow,
partial path or selective methods ... the most detailed view
available. This reports will ensure that a product is truly
"market ready" before it is launched.
Additional Features:
- Thread Status - Provides the current status of each thread running in the Ruby process (sleep, run, wait), as well as the current method being executed at the time the thread status command is invoked. Screenshot
- Thread Dump - Obtain a full stack trace by terminating threads in the Ruby process.
- RSS Content - RubyRunCE provides optional RSS content, "pushing" regular updates of metrics (such as Request Performance Breakdown and Transaction Throughput).
- Memory Leak Suspect - Track down potential memory leaks by viewing the top 20 Ruby class names in an object map. Screenshot
Download Now!