Have seen type 3 more often than any other in my Ruby life. Particular culprits are “web server doing something which is maybe not really an interactive job if you think hard” like e.g. crunching reporting data on an account. The solution for me has always been restarts.https://twitter.com/nelhage/status/990710731258540033 …
-
-
Worth knowing: depending on how you route requests to web server processes having one process which has a 15s request rather than your typical 200ms can cause many of your regular requests to take 15.2s as they queue up unhappily behind the long request, and this is vewwwy quiet.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I'm not sure I want to think about how much of my dev life has been spent reengineering web routes into async background jobs, keeping the user in the loop and serving the results. Or maybe this should be my refocussed svc offering, "I'll speed up your reports display pages!"
Thanks. 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.