I know about the disadvantages of the single thread model, even thinking
about delegating heavy stuff to Rust now that it is stable
On Tue, May 19, 2015 at 1:53 AM Ryan Graham wrote:
> If there is a process per CPU core, and the same process always runs on
> the same core, the result is generall
If there is a process per CPU core, and the same process always runs on the
same core, the result is generally *less* context switching. But that
effect is nothing compared to the reason for the 1 worker per core
recommendation.
While node uses multiple threads behind the scenes, only one of those
I see many articles saying to spawn workes equal to CPU cores, but what
about context switching cost?
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules:
https://github.com/joyent/node/wiki/Mailing-List-Posti
