3 ms·

Wow, amazing find. I've been struggling with this issue for many months, and I just figured it was rails 3.0 fault for being so big and bloated. Now we find out

Wow, amazing find. I've been struggling with this issue for many months, and I just figured it was rails 3.0 fault for being so big and bloated. Now we find out it's ruby implementation. I really hope this patch makes it in. I've patched my local copy. Feels like I have doubled my computer speed! Seriously though, I can't believe the fix was so easy, and the ruby core hasn't done something about this yet. The last major external fix to ruby was with the REE people, and that still hasn't made it back into MRI. So I'm a bit worried this patch will get rejected and the problem won't be fixed.

joevandyk 15y ago
Rails does have problems with 3.0 being slow. See http://www.youtube.com/watch?v=kWOAHIpmLAI&t=34m9s http://www.youtube.com/watch?v=kWOAHIpmLAI&t=34m9s for a recent talk on it by @tenderlove.
- dhh 15y ago
  tenderlove is going to follow up on this. The issue is for metal-like responders, not for full-fledged apps. We've lost a couple of ms on the low-end due to the stack issue.
nestlequ1k 15y ago
As a followup, while this patch works great, using it forces you onto ruby-head which breaks a ton of shit. I'm back to shit rails bootup speeds for now. But at least I now have hope that it's possible that a fix may be on the horizon. joevandyk posted a great example project here: https://github.com/joevandyk/slow-rails https://github.com/joevandyk/slow-rails 20second bootup of an empty project = hair on fire omgwtf issue. the start of phpenvy? (no, not really)