Friendly reminder that if you implement DCI with instance-specific mixins you're blowing your method cache every time
@raggi @urbanautomaton yeah, I think something people don't grasp is that busting the method cache affects the whole app
-
-
@bascule@urbanautomaton if you do it every request, everything is shot slow basically all the time. Maybe arrays are "OK" -
@raggi@urbanautomaton do you know of any tools for tracking down method cache breakers in a large app? -
@bascule@urbanautomaton module kernel def extended p caller; super; ... -
@raggi@urbanautomaton I don't think that works, and it wouldn't catch every case where you could bust the method cache
End of conversation
New conversation -
-
New conversation
-
-
-
@bascule@raggi@urbanautomaton wait, does class << self bust the method cache *always* or only if you’re being a jerk?Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule@urbanautomaton but then stack depth of 60 on MRI x64 is a 100% runtime cost for GC stack scansThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.