News for hackers. Stuff that matters.
Re:Patching Rails Performance by schneems on Thursday August 06, 2015 @07:11PM (#10020047)
> I've been impressed with the performance work you've been doing across the board

Thanks!

For all the tests I used MRI Ruby 2.2.2. Unless otherwise noted, I almost exclusively use the most recently released MRI Ruby version for testing. There shouldn't be a huge difference in most recent Ruby versions. The only thing that comes to mind is that `String#freeze` existed in older versions but was a method call, and not implemented as a parsing optimization (i.e. it would still allocate a string) however I believe that's been in there for a few years. Maybe the generational GC might have an impact.

> It'd be helpful to know what your GC tuning looks like, too.

I used stock GC settings for all the benchmarks

``` $ env | grep GC # nothing here ```

> A little expansion on the methodology would just make it all the more valuable.

The patch does have some more specifics than the post, especially the commits. I used benchmark/ips in some of them to demonstrate specifics problems. I can do a larger write up on specific methodology, if you think that would be interesting.

> If you press 'y'

Thanks, i've been trying to get in the habit of doing so, that's a good tip.

Re:Patching Rails Performance by nirvdrum on Thursday August 06, 2015 @07:16PM (#10020062)
> For all the tests I used MRI Ruby 2.2.2. Unless otherwise noted, I almost exclusively use the most recently released MRI Ruby version for testing.

Good to know. I guess I'm suggesting that specifically calling that out in the text will help it stand the test of time. Otherwise the reader needs to cross-reference the date with the MRI release list.

And really, this is all I was looking for in the methodology. The post covers what you did in pretty good detail. The GC thing was something I was curious about just because that's ping-ponged quite a bit throughout the 2.x releases.

Thanks again!