4 ms·

Was your benchmark for requests/sec or connections/sec?

• lstodd 8y ago
  Single-request connections. Response required consulting memcached and updating it from postgres if out of luck, which was very rare but still needed (and patching then-existing postgres C client to be async aware was an undertaking)
  • jasonlotito 8y ago
    > Single-request connections. What does that mean? You keep qualifying "connections." It's a connection. It holds onto it's connection for X period of time. An HTTP request is just a single-request connection, which is NOT what this article is discussing.
    • lstodd 8y ago
      One HTTP connection, one request, one response, connection closed. I admit I didn't first see that they actually don't do any i/o over those connections. Well, you know, handling x accepts() per second and holding onto y fds is even less than nothing to be proud of.
      • jasonlotito 8y ago
        So yeah, those are generally considered to be requests per second. Apples and oranges.