Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
nodejs
Home
+ new post
About this group
Join this group
Message from discussion Sane arguments for when you shouldn't use node.js? (no trolls please)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Matt  
View profile  
 More options Oct 7 2011, 11:04 pm
From: Matt <hel...@gmail.com>
Date: Fri, 7 Oct 2011 23:04:56 -0400
Local: Fri, Oct 7 2011 11:04 pm
Subject: Re: [nodejs] Re: Sane arguments for when you shouldn't use node.js? (no trolls please)
Print | View thread | Show original | Report this message | Find messages by this author

On Fri, Oct 7, 2011 at 10:51 PM, Liam <networkimp...@gmail.com> wrote:
> Is there a difference between handing off cpu-intensive stuff to a
> subordinate thread/process vs doing it inline on one of several load-
> balanced processes running the same code?

> In neither case do you stall the main request processor.

It's not about stalling the event loop. That's a solved problem. The problem
is in passing data between the two, requiring copies to be made, and
potentially sending large amounts of data over pipes.

Threads get around this by having access to the same memory space (at the
expense of having to learn how to use locks).

But personally I believe this is all pretty overblown. If you have something
that is going to take enough time that you need to get it outside of the
event loop, then the overhead of passing the data back and forth is likely
to be minimal in comparison.

It's still one of those issues where Node will be criticised though.

Matt.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google