Top all-time · #7309
caustik's blog
Personal blog · blog.caustik.comprogrammingsystems
caustik's blog is a personal blog at blog.caustik.com about programming and systems. Since 2012, 11 different Hacker News readers have linked it 16 times, most often “NodeJS with 250k Concurrent Connections”. The last post was in 2016, but the archive is still widely read.
Too few sampled comments (5) to say how often HN recommends it.?
Why HN links it
HN readers link this blog's 2012 posts on scaling a single Node.js server to 100k, 250k and 1M concurrent connections, plus a tip on getting past the V8 heap limit.
Summarised by Claude from a sample of 5 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- NodeJS with 250k Concurrent Connections5 people · 5 mentions · first linked 2012-04-10
- Node.js w/1M concurrent connections2 people · 2 mentions · first linked 2012-08-19
- Scaling node.js to 100k concurrent connections2 people · 2 mentions · first linked 2012-04-10
What Hacker News says?
There are ways around that: http://blog.caustik.com/2012/04/11/escape-the-1-4gb-v8-heap-...
Comment linking /2012/04/11/escape-the-1-4gb-v8-heap-limit-in-node-js/
on “Node.js in Flame Graphs”Submitted Scaling node.js to 100k concurrent connections as a story · 64 points
HN discussionSome dude in 2012 did 1 million active connections with whatever node.js and v8 versions we had at that time :) http://blog.caustik.com/2012/08/19/node-js-w1m-concurrent-co... Edit: I wasn't aware but there was some build-up to it: - 100k connections: http://blog.caustik.com/2012/04/08/scaling-node-js-to-100k-c... - 250k connections: http://blog.caustik.com/2012/04/10/node-js-w250k-concurrent-...
Comment linking /2012/04/10/node-js-w250k-concurrent-connections/
on “600k concurrent websocket connections on AWS using Node.js (2015)”Submitted Node.js w/1M concurrent connections as a story · 13 points
HN discussionIt seems to me it's not because the Node.js test used a remote machine to drive the connections whereas this one is driving the connections from the same machine. Running the server and test harness on the same machine bypasses a whole lot of networking stack. Also, it seems the limitation in Node.js is the maximum heap size of around 1.4GB [1]. This test used a heap size of 3GB which is just not possible in Node (u…
Comment linking /2012/04/10/node-js-w250k-concurrent-connections/
on “600K concurrent HTTP connections with Clojure and http-kit”Submitted Node.js w/1M concurrent connections as a story · 4 points
HN discussionLink to his next post showing him breaking 250k - http://blog.caustik.com/2012/04/10/node-js-w250k-concurrent-...
Comment linking /2012/04/10/node-js-w250k-concurrent-connections/
on “Scaling node.js to 100k concurrent connections”Submitted NodeJS with 250k Concurrent Connections as a story · 2 points
HN discussionThis guy has some nice posts of scaling a single node.js server up to 1m connections: http://blog.caustik.com/2012/08/19/node-js-w1m-concurrent-co... http://blog.caustik.com/2012/04/10/node-js-w250k-concurrent-... http://blog.caustik.com/2012/04/08/scaling-node-js-to-100k-c... http://blog.caustik.com/2012/04/06/node-js-scalability-testi...
Comment linking /2012/04/06/node-js-scalability-testing-with-ec2/
on “What is the theoretical maximum number of open TCP connections? (2010)”Submitted Scaling node.js to 100k concurrent connections | caustik's blog as a story · 2 points
HN discussionSubmitted Scaling node.js to 250k concurrent connections as a story · 1 points
HN discussion