Re:NODE.JS CAKE: Removing Technical Limitations and Develope...
by robtweed on Monday April 24, 2017 @01:45PM
(#14186333)
You're right - the QEWD architecture is as you describe, and not that unusual, though I'm not aware of anyone else having implemented such a design with Node.js. I'm not sure there was a good reason for Node's not using something similar, but then again, I'm not really proposing that Node.js should be like QEWD. The fact is I've been able to implement QEWD's architecture using standard Node.js capabilities. So it provides a way of working around the deficiencies of Node that are a direct result of its intentional architecture, if that's what you want to be able to do - best of both worlds.
Not sure I understand your GC questions, sorry?
Is there a prefork-friendly GC for Javascript? I know this was a major issue with the many-single-threaded-app-servers approach in the Ruby ecosystem; previous versions of the GC algorithm kept GC metadata in the same pages as data, preventing the CoW memory sharing that prefork servers ideally prefer.