------art_30603_26676182.1151881705131
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 7/2/06, M. Edward (Ed) Borasky <znmeb / cesmail.net> wrote:
>
> Francis Cianfrocca wrote:
> > My experience suggests that Ruby's performance "problems" are negligible
> > with small working sets and are very serious with large ones (program
> > size
> > and number of code points seem to matter relatively little). My
> > hypothesis
> > (no proof adduced) is that this is a necessary consequence of Ruby's
> > extremely dynamic nature and is only somewhat amenable to improvements
> > like
> > YARV and automatic optimizations (as the many Java-like VM proponents
> > suggest).
> Interesting ... maybe we shouldn't be profiling Ruby code with the
> *Ruby* profiler, but profiling the Ruby *interpreter* with "gprof" or
> "oprofile". I had assumed that had already been done, though. :)


I heard a rumor that Ruby's heavy use of setjmp/longjmp interferes with
profiling in some way, but I could have been misinformed or confused. Can
anyone confirm that?

-- 
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ www.jruby.org
Application Architect @ www.ventera.com

------art_30603_26676182.1151881705131--