@bascule You know exactly why it was pegging the goddamn CPU. :\
-
-
-
@KirinDave not having access to their app I don't have that information, no, but my best guess would be MRI's GC -
@bascule Yes. 90% of the time that is the damn problem. Or overhead from higher order patterns using blocks. -
@KirinDave another potential answer: shitty code -
@bascule Plenty of shitty code is plenty fast.
End of conversation
New conversation -
-
-
@bascule my thoughts too. also wondering how their costings are working if 30 servers is "so much money"Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule lolderpThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule lololol almost same impression that I had in the morningThanks. 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.