Node Server Memory Increasing Doubts?

  node.js, question
var http = require('http');
 http.createServer(function (req, res) {
 res.writeHead(200, {'Content-Type': 'text/plain'});
 res.end('Hello World\n');
 }).listen(3002);
 console.log('Server running at http://127.0.0.1:3002/');

test result

After the server is turned on, the memory takes up 5M after the first access. after using AB stress test for a period of time, the memory soared to 87M, and the memory is basically fixed to this level. if so, do you still dare to use node.js as the background of a large server? At present, more than half of the projects have been developed, and memory test is not ideal either. It’s so tangled.

Before, when the Shadowsocks-nodejs branch was abandoned, I saw an explanation about the GC of the V8 engine, the GC of the V8:Githubsue’s comments

Node.js encountered more problems with memory than with too much memory … ……V8 has a practical limit on the heap size by default, 1.4G under 64bit and 0.7G under 32bit, in case GC takes too long. “Node.js” inside has a special chapter on memory.

But I don’t think this is a problem for “large servers” … besides, high memory usage doesn’t mean low efficiency, and I don’t think Node.js takes up much more horizontally …