-
-
Replying to @urbanautomaton
@urbanautomaton@raggi grep for "extend" on an object2 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@urbanautomaton it's probably actually in haml-rails somewhere, it's certainly partial related. we solved this crap in tilt tho1 reply 0 retweets 0 likes -
Replying to @raggi1 reply 0 retweets 0 likes
-
Replying to @urbanautomaton
@urbanautomaton@bascule lots and lots of things do this. Rails tests in real apps aren't that slow because ruby or because rails.3 replies 0 retweets 0 likes -
Replying to @raggi
@raggi@urbanautomaton@bascule the biggest issue is the effect on a real app is much more significant than microbenching says1 reply 0 retweets 0 likes -
Replying to @raggi
@raggi@urbanautomaton yeah, I think something people don't grasp is that busting the method cache affects the whole app4 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@urbanautomaton if you do it every request, everything is shot slow basically all the time. Maybe arrays are "OK"2 replies 0 retweets 0 likes -
Replying to @raggi
@raggi@urbanautomaton do you know of any tools for tracking down method cache breakers in a large app?2 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@urbanautomaton module kernel def extended p caller; super; ...1 reply 0 retweets 0 likes
@raggi @urbanautomaton I don't think that works, and it wouldn't catch every case where you could bust the method cache
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.