Take the tour ×  When I listen for a client connection in
Socket.IO, there seems to be a latency of 8-9 seconds as it
falls back to XHR. This is too slow for most purposes, as I'm
using Socket.IO to push data to users' news feeds, and a lot can
happen 8 or 9 seconds.  Is there any way to speed up this
failure?   After deploying to Nodejitsu's VPS I tried this again
and the socket connection was nearly immediate (enough that a
user wouldn't notice). I'm only experiencing this on my local
machine. So the question may actually be: why is it so slow on
my local machine?  share|improve this question what setup does
your local machine have? –  Alfred Feb 1 '12 at 21:18 add
comment  1 Answer  This question is almost impossible to answer
without more information on your local setup, but it's
interesting that you're failing over to XHR. The following
question might explain why it's failing over to XHR, but not if
you're able to use the same browser successfully once it's
published.  Socket.io reverting to XHR / JSONP