title: Overcome node.js memory limit with fork() ?
body: <p>According to my knowledge most node.js versions have memory limit for each process around 1GB, based on this information:</p>
  
  <blockquote>
    <p>Currently, by default v8 has a memory limit of 512MB on 32-bit systems, and 1.4GB on 64-bit systems.
    <a href="https://github.com/nodejs/node-v0.x-archive/wiki/FAQ" rel="nofollow">https://github.com/nodejs/node-v0.x-archive/wiki/FAQ</a></p>
  </blockquote>
  
  <p>It is an old archive, things may have improved since. However, what I am interested about is if one is about to use</p>
  
  <pre><code>require('child_process').fork("newProcess.js")
  </code></pre>
  
  <p>Is it possible to overcome this limitation? </p>
  
  <p>Thus creating a new V8 instance would create a new memory pool for JavaScript Objects. </p>
  
  <p>The reason I am asking is that I could not find a reliable source exactly confirming this case, even though the documentation strongly suggests that this would be the case because it states:</p>
  
  <blockquote>
    <p>These child Node.js processes are still whole new instances of V8.</p>
  </blockquote>