Re: profilier issues???

< :the previous in number ^ :the list in numerical order > :the next in number P :the previous (in thread) N :the next (in thread) |<:the top of this thread >|:the next thread ^ :the parent (reply-to) _:the child (an article replying to this) >:the elder article having the same parent <:the youger article having the same parent ---:split window and show thread lists | :split window (vertically) and show thread lists ~ :close the thread frame .:the index ..:the index of indices

Lothar Scholz wrote:

>Welcome to the world of "proof-of-concept" ruby tools.
>
>The profiler and the debugger are implemented in an extremly bad ways.
>It is not a problem to increase the performance by a factor 100.
>
>I'm currently working on the debugger issue. Profiler will come later.
>
>At the moment the only possibility is to reduce the data size in your
>application or split it into a few testcases. I know it removes most of the
>usefullness of profiling, which should be done on real world data. But
>at the moment there is no way to do this.
>

Isn't your company trying to build a ruby debugger to sell?

Michael