3 ms·

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

• ramoq 18y ago
  What the heck is that picture?
  • timtrueman 18y ago
    It's the brain bug from Starship Troopers.
  • vaksel 18y ago
    I think thats the brain bug from starship troopers
  • dustmop 18y ago
    It's afraid.
  • octane 18y ago
    It's what you don't want to wake up next to after a night of drinking.
• bcl 18y ago
  dupe
• kubrick 18y ago
  Dupe or not -- anyone know if this equally applies to Ruby 1.9? I've started using it full-time now for my Rails apps (2.3.2) and the speed boost is serious. Another 30% ... wow.
• kubrick 18y ago
  The answer to my question (does this work with 1.9?) is no -- YARV requires pthreads. So for a much more than 30% performance boost, switch to Ruby 1.9. It's more like a 4X performance boost.
• Bjoern 18y ago
  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.
  • Freaky 18y ago
    > 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.
• batasrki 18y ago
  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.
  • deleted 18y ago
    [deleted]
• piramida 18y ago
  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 :)
  • Confusion 18y ago
    Fortunately there will then be a huge demand, and hence a large reward, for people to invest time into learning it once more.
• deleted 18y ago
  [deleted]