Home/ Questions/Q 7761745
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T14:12:58+00:00

Take the same code that sits on nodejs.org home page. Serve a static file

  • 0

Take the same code that sits on nodejs.org home page. Serve a static file that is 1.8Mb. And do the same with Nginx, and watch the difference.

Code : http://pastie.org/3730760

Screencast : http://screencast.com/t/Or44Xie11Fnp

Please share if you know anything that’d prevent this from happening, so we don’t need to deploy nginx servers and complicate our lives.

ps1. this test is done with node 0.6.12. out of curiosity, i downgraded to 0.4.12 just to check if it’s a regression, on the contrary, it was worse. same file used 25% twice.

ps2. this post is not a nodejs hate – we use nodejs, and we love it, except this glitch which actually delayed our launch (made us really sad), and seemed quite serious to me. i’ve never read, heard, seen or expected to come across.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The problem with your node benchmark is that you store the static file in a variable inside the V8 heap. Due to the way how V8 handles memory it can’t directly send data contained in javascript variables to the network, because addresses of allocated objects may change during runtime, therefore V8 has to make a copy of your 1.8MB string on every request, sure that kills performance.

    What you could do is to use a Buffer:

    replace: longAssString = fs.readFileSync(pathToABigFile, 'utf8');

    with: longAssString = fs.readFileSync(pathToABigFile);

    that way you have your static file in a buffer, buffers are stored outside of V8s heap and require no copy when sent to the network and should therefore be much faster.

    • 0