Fix a bug in Ruby’s configure.in and get a ~30% performance boost

timetobleed.com

60 points·vaksel··11 comments

This post (and the blog overall) shows how the forgotten art of tracing/debugging executables can seriously affect web 2.0 community - when the last person who knew assembly will retire we are all doomed :)

Fortunately there will then be a huge demand, and hence a large reward, for people to invest time into learning it once more.

The post's title is misleading, since this only affects threaded Ruby programs, not all of them.

It's a good patch and the author knows his stuff, so there's no need for sensationalist titles.

What the heck is that picture?

It's the brain bug from Starship Troopers.

I think thats the brain bug from starship troopers

It's afraid.

It's what you don't want to wake up next to after a night of drinking.

dupe

30%. Thats, insane. Oh wait, its for the MRI (Matz Ruby Interpreter). Hm, that makes this news for me a tad less interesting because everybody is already running 1.9 (yarv)?

Patching MRI is nice but a switch to 1.9 has more benefits than just speed.

> everybody is already running 1.9 (yarv)?

Nope, no more so than everybody is already running Python 3.

It's only for pthread linkage, anyway; it's avoiding a 30% performance loss, not giving everyone a 30% performance gain.

Reply on news.ycombinator.com