[mbbrutman]

It's still beeping ... busy != dead. Right now it's getting hammered pretty hard. I haven't implemented the clustering and load balancing yet.

It can serve 8 concurrent connections but that slows it down. It will queue a few more too; be patient and you will be rewarded.

[wvenable]

It actually works for me if you just wait long enough for it load. Which, at this point, is very impressive.

[mbbrutman]

Yep, at this point it's just continually busy.

For the next iteration I've got to put a better Ethernet card on it. The Xircom PE3-10BT device is nice because it's convenient, but the bandwidth would be 2x higher with a real Ethernet card on the bus.

And normally this machine is idle so the speed and bandwidth are not a problem. Right now it's very popular. :)

[lucb1e]

What kind of speed does that Xircom get?

I don't know what's on the site, maybe it's busy uploading data to various people, but usually the original 10mbps ethernet is enough to serve most ~light websites (anything that is not as heavy as youtube or an image blog basically) to the hacker news homepage, and I'm not getting synacks so this is not the web server (layer 7) being slow

[mbbrutman]

The Xircom is pretty bad, as it costs a lot to do the I/O through the parallel port. Just using TCP/IP sockets (no disk access or processing) the machine can send and received about 42KB/sec. A better adapter can do nearly 3x that on the same machine.

Performance measurements here: https://www.brutman.com/mTCP/mTCP_Performance.html

[anyfoo]

So about 1Mbps max with a good adapter? Wow, more than I thought... yeah, a hard disk of the era, not even AT bus, most likely won't be able to keep up with that, heh.

[anyfoo]

I'm repeating myself a bit, but, dude, it's an 8088 (EDIT: ok, technically a NEC V20, pretty negligible though). It has an 8 bit wide bus. It runs at 4.77MHz and needs many cycles (at least 4? more?) per instruction. With a parallel port adapter, not even an 8 bit ISA one. I haven't done the math, not even on an envelope, but I somehow doubt the Ethernet adapter is the bottleneck here...

[lucb1e]

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

[anyfoo]

"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.

[mbbrutman]

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.

[basementcat]

May be fun to listen to a recording of the beeps.

[mbbrutman]

I took 30 seconds of video with the beeping and the screen scrolling for posterity. I'll get it posted somewhere.