←back to thread

67 points anon6362 | 2 comments | | HN request time: 0s | source
Show context
alexdns ◴[] No.45074520[source]
It was considered innovative when it was first shared here eight years ago.
replies(1): >>45074700 #
nurumaik ◴[] No.45074700[source]
Anything more innovative happened since (honestly curious)?
replies(4): >>45075146 #>>45075479 #>>45075495 #>>45077234 #
js4ever ◴[] No.45075146[source]
I don't think so, but my guess is raw performance rarely matters in the real world.

I once explored this, hitting around 125K RPS per core on Node.js. Then I realized it was pointless, the moment you add any real work (database calls, file I/O, etc.), throughput drops below 10K RPS.

replies(3): >>45075358 #>>45075454 #>>45075994 #
1. jandrewrogers ◴[] No.45075454[source]
Storage and database doesn’t have to be that slow, that’s just architecture. I have database servers doing 10M RPS each, which absolutely will stress the network.

We just do the networking bits a bit differently now. DPDK was a product of its time.

replies(1): >>45086643 #
2. js4ever ◴[] No.45086643[source]
What DB engine is it? What hardware?