You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Something wrong with the implementation of the "promise.then" #3414
V8 promises haven't been optimised at all. It's on our agenda once our ES6 support is feature complete.
V8 promises support various callback hooks into devtools, which cause a certain overhead.
Alternative promise implementations tend to take shortcuts relative to the official ES6 semantics (e.g., goog.Promise.all you use below does not support subclassing correctly).
We assume that (1) is the main factor, and will go away eventually, but due to the others some (hopefully minor) differences might remain.
If you have further questions/concerns, I would recommend participating over there. (Promises aren't in Node core. They're supplied by v8.)
Activity
thefourtheye commentedon Oct 17, 2015
Most likely a v8 thing, as Node.js uses underlying v8's
Promiseimplementation.benjamingr commentedon Oct 18, 2015
Yes, native promises are slower and consume more memory than bluebird promises, this is a well known fact. I think the issue can be closed.
Trott commentedon Oct 18, 2015
According to this from the v8 mailing list:
If you have further questions/concerns, I would recommend participating over there. (Promises aren't in Node core. They're supplied by v8.)