Hacker News new | ask | show | jobs
by lucb1e 1065 days ago
I'm not getting a SYNACK back from it within the default firefox-on-linux timeout of 60 seconds. Guess I'm obliged now to run Wireshark for the next hour to prove a point just in case it does respond to that (interplanetary latency style), but I'm going to call that at least fairly dead

Edit: actually, I'm not sure how long my router will keep a half-open tcp connection in its state table. It may not show up in Wireshark on my laptop. 10 minutes in, no synack showing up: I'm calling it
1 comments
anyfoo 1065 days ago
"Dead" for me is if it actually crashed and does not recover without interference. I'm not surprised that an 8088 (not even an 8086!) will either take a really long time to reply SYNACK, or just drop packets entirely when the queue is full, when hammered with HN levels of crowds.

It may be dead, but it also may just be busy.

link
mbbrutman 1065 days ago
A few things to consider here:

  * It's getting hammered.  I didn't expect it to be this bad.
  * If it can't process things fast enough packets might be dropped.  So the TCP/IP error rates are probably pretty high right now.
  * It's logging all of this crap too ...
Normally it can do the handshake in tens of milliseconds. Right now the load on it is basically "crush." But it's queuing and answering as best as it can.
link