There has actually been a lot of movement on this lately so I'd say the perf
differences are a giant question mark. The last numbers anyone did showed some
pretty bad numbers for promises but I know they've done a bunch of perf work
lately so it might be better now.
On Dec 13, 2013, at 4:35AM,
Thank you - this is an excellent writeup and analysis - exactly what we needed
to know
Sent from my LG Mobile
Scott González wrote:
>See
>http://spion.github.io/posts/analysis-generators-and-other-async-patterns-node.html
>for
>an analysis of the various async patterns and modules.
>
>
>On Thu
See
http://spion.github.io/posts/analysis-generators-and-other-async-patterns-node.html
for
an analysis of the various async patterns and modules.
On Thu, Dec 12, 2013 at 2:51 PM, john.tiger wrote:
> looking at 2 code approaches to using Passport w/ Angular - one with
> promises, one with callba
On 12/12/2013 11:47 PM, Trevor Norris wrote:
For your general program, probably not. It's only in tight loop scenarios when
you'll feel the affects. Which usually only occurs in benchmarks. Meaning, your
CPU will need to be pegged during the run.
okay, thks - assuming this is right, that's all
For your general program, probably not. It's only in tight loop scenarios when
you'll feel the affects. Which usually only occurs in benchmarks. Meaning, your
CPU will need to be pegged during the run.
Now, to nip in the bud the religious flame war that would probably ensue. Let's
not all post
looking at 2 code approaches to using Passport w/ Angular - one with
promises, one with callbacks - any speed difference to be concerned with ?
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this mess
