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 …
-
-
Then you do a bit of work on front end to kick off job and poll for status rather than just “run query and maybe render page or maybe timeout.” This in very unglamorous engineering but it is often both better UX and stops systemwide issues stemming from teeny portion of app.
Show this thread -
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 thread
End of conversation
New conversation -
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.