ruby optimization

suggest creating a github issue those get looked at, move the conversation there :) On Friday,

Problem solved. If you are interested in details look at the discussion: https://github.com/ruby-prof

OK any other followers feel free to chime in here, I guess I just haven't done precompiled in so

i wonder how that caused a recursion issue...hmm... On Sun, Jun 8, 2014 at 10:51 AM, Grant Schoep

I know it supported it with the 1.9.x and a "patched' GC I wonder if the patch still works [

So you basically want something like 20.times { run_my_program } ObjectSpace.each_object{|o| p o.

For the googlers: I added require 'ruby-prof' to the production.rb, that helped. Maybe there

What do you mean by an object's "memory size usage"? Are you looking for memory

Hi, someone already fixed this by the same solution. https://github.com/ruby-prof/ruby-prof/pull/126

Hi, to correctly implement this, the call_info.children and call_info.parent would have to point not

Hi all, I have been looking into whether it is possible to invert the behavior of the excluded

Yes. I am testing both now. When both are enabled is something fun in ruby-prof logs :). What I see

I am guessing that it is related to this bug here: https://github.com/rdp/ruby-prof/issues/86 Which

I think you're seeing the same thing as this other fella did: https://groups.google.com/forum/?hl

What about older versions like 0.9'ish? On Mon, May 28, 2012 at 8:37 PM, Craig Walker <craig@

Hey Caleb, Thank you for the in-depth investigation and response. Indeed Mongoid is taking some

On 06/02/2011 08:42 PM, Roger Pack wrote: > Interesting. Actually my current thoughts were

On Sat, Apr 23, 2011 at 12:41 AM, Kurt Stephens <kur...@gmail.com> wrote: Sorry, forgot to

"Charles Oliver Nutter" <hea...@headius.com> wrote: > Caleb Clausen <caleb@

On Fri, Jun 18, 2010 at 11:46 AM, Roger Pack <roger...@gmail.com> wrote: >> namespace

Roger Pack wrote: >> # coding: utf-8 >> Polyglot.dialect :macro >> Macro.require

Yeah It's something in the admin stuffs for rubyforge...somewhere... On Thu, May 13, 2010 at 4:23

>> Yeah if you use the GoogleHashSparseIntToInt it's said to use "2 bits >> per

So it turns out that blocks *are* optimizable...well, certain ones are at least :) It appears from

> Bad news: > it blew up (size wise) with larger arrays. > http://groups.google.com/group/

Nope that's the one :) Speaking of optimizations...I saw some interesting rubinius benchmarks the

> ... > with a "cheat" to not have to call #hash on the object itself: > > case

After experimenting a bit with the ruby2cext/crystalizer [1] I'm wondering if what it does wouldn

As an attempt to optimize for MRI's GC and move elements into hash, my first attempt is

rogerdpack wrote: > My next question is...why is regex lookup on 1.9 twice the speed of > 1.8?