Performance patch for ruby 1.9.3-p385

patch_for_p385.md

Patch for ruby 1.9.3-p385 without backport-gc:

• https://github.com/funny-falcon/ruby/compare/p385...p385_falcon.diff
• https://github.com/funny-falcon/ruby/compare/p385...p385_falcon

Patch for ruby 1.9.3-p385 with backport-gc:

• https://github.com/funny-falcon/ruby/compare/p385...p385_falcon_gc.diff
• https://github.com/funny-falcon/ruby/compare/p385...p385_falcon_gc

rbenv instructions https://gist.github.com/samgranieri/4772546

Separate patches:

1. backport speedup of require: https://github.com/funny-falcon/ruby/compare/p385...p385_backport_speedup_require
2. backport gc: https://github.com/funny-falcon/ruby/compare/p385...p385_backport_gc
3. array as queue: https://github.com/funny-falcon/ruby/compare/p385...p385_ary_queue
4. hash optimisations: https://github.com/funny-falcon/ruby/compare/p385...p385_st_opt
5. namespace optimisations: https://github.com/funny-falcon/ruby/compare/p385...p385_sparse_array
6. hash optimisation + namespace optimisations: https://github.com/funny-falcon/ruby/compare/p385...p385_st_opt_sparse_array

@johnl could you try again? @tmm1 just found memory leak which affects #methods #instance_methods , I've updated patches (sparse_array, st_opt_sparse_array, falcon and falcon-gc, for this version only)

@johnl if memory leak remains, tell me the way to reproduce it.

I found two memleaks in class.c, introduced by the sparse array patch:

Here's a fix: skaes/rvm-patchsets@1f94ce6

Ah, sorry, you already found these, I think.

@skaes, excuse me that I'm not pushes it for you. I was busy at work and didn't found time to do it.