It might, if the code can be optimized. There are all sorts of reasons why it might not. For example, at one point in time, a switch statement with more than 128 cases could not be optimized.
https://github.com/petkaantonov/bluebird/wiki/Optimization-k...
In Oven: The Company Behind Bunpetkaantonov
bluebird
JavaScript2013–2022
petkaantonov / bluebird
bluebird
:bird: :zap: Bluebird is a full featured promise library with unmatched performance.
66Distinct people
87Mentions
2Explicit recommenders
20.5KGitHub stars
What to know before exploring
What it is
:bird: :zap: Bluebird is a full featured promise library with unmatched performance.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
The examples are very far from the JS I see and read, but this is definitely a very useful tool. It seems like gcc -Olevel. It would be interesting to incorporate some sort of…
jamescostian used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- kriskowal/q · linked in 3 of the same discussions
- tj/co · linked in 3 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year87 dated mentions
Observed mentions: 2013-10-04 10:29:42 UTC to 2022-08-24 21:34:55 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 8 | 2 | 6 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 33 | 5 | 28 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 23 | 3 | 20 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 17 | 3 | 14 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Got a question? Join us on stackoverflow, the mailing list or chat on IRC
Introduction
Bluebird is a fully featured promise library with focus on innovative features and performance
See the bluebird website for further documentation, references and instructions. See the API reference here.
For bluebird 2.x documentation and files, see the 2.x tree.
⚠️Note⚠️
Please use native promises instead if at all possible. Native Promises have been stable in Node.js and browsers for around 10 years now and they have been fast for around 7. Any utility bluebird has like .map has native equivalents (like Node streams' .map).
This is a good thing, the people working on Bluebird and promises have been able to help incorporate most of the useful things from Bluebird into JavaScript itself and platforms/engines.
If there is a feature that keeps you using bluebird. Please let us know so we can try and upstream it :)
Currently - it is only recommended to use Bluebird if you need to support really old browsers or EoL Node.js or as an intermediate step to use warnings/monitoring to find bugs.
Questions and issues
The github issue tracker is only for bug reports and feature requests. Anything else, such as questions for help in using the library, should be posted in StackOverflow under tags promise and bluebird.
Thanks
Thanks to BrowserStack for providing us with a free account which lets us support old browsers like IE8.
License
The MIT License (MIT)
Copyright (c) 2013-2021 Petka Antonov
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
Read the full README on GitHubWhat Hacker News says
87 sourcesThere is nothing wrong with using new Array() to construct array of known capacity. By default, I think JS literal arrays will have a capacity of 4, so especially if you know you will have less than four elements, or a non power of two number of elements, this can be seen as a micro-optimization. `bluebird` uses new Array() extensively, e.g.
https://github.com/petkaantonov/bluebird/blob/12154adb501660...
In Avoid Using New Array() in JavaScriptAny team with enough developers using Node should develop a handful who can understand the v8 internals and help troubleshoot real-world performance problems.
The most helpful resource I've found about v8 specific performance is the bluebird optimization killers wiki:
https://github.com/petkaantonov/bluebird/wiki/Optimization-k... wiki, and the v8 bailout reasons repo: https://github.com/vhf/v8-bailout-reasons
In JavaScript and Node performance coding tips to make applications fasterYou're using poor polyfills if they use setTimeout. Good polyfills [1] use MutationObserver which uses the (a?) microtask queue.
Invoking a Promise's then() callback synchronously is a violation of the spec. IIRC there are some tests to prevent that in the test suite.
[1]: https://github.com/petkaantonov/bluebird/blob/2c9f7a44/src/s...
In Async Iterators: These Promises Are Killing My PerformanceThe examples are very far from the JS I see and read, but this is definitely a very useful tool. It seems like gcc -Olevel. It would be interesting to incorporate some sort of tailoring for JS engines into this, like how a compiler might try to make x86-specific optimizations. For example, if you know your target audience mostly runs Chrome (or if the code is to be run by node), you might apply optimizations to change the code to be more performant on V8 (see https://github.com/petkaantonov/bluebird/wiki/Optimization-k... for example).
I love it and can't wait to use it on some projects!
In Prepack helps make JavaScript code more efficientthis [1] is probably what you want
1. https://github.com/petkaantonov/bluebird/wiki/Optimization-k...
In V8: A Tale of TurboFanOh you're right. https://github.com/petkaantonov/bluebird/blob/master/src/pro...
In Node v6.9.0 (LTS)This is indeed true for V8 IIRC, but even if it weren't, both arguments.length and arguments[x] are safe to use without stopping optimisation, so even a very cautious JavaScript dev can effectively clone the arguments object in a roundabout sort of way and pass it to apply, like so:
// given a context and function 'func'
var args = [];
for(var i = 0; i < arguments.length; i++){
args[i] = arguments[i];
}
func.apply(context, args);
Source: https://github.com/petkaantonov/bluebird/wiki/Optimization-k...
In Why I write plain JavaScript modulesGlad this submission is being upvoted but I think there is room for more practical and direct advice. Here are some resources for JS:
- https://github.com/petkaantonov/bluebird/wiki/Optimization-k...
- https://github.com/amark/gun/wiki/100000-ops-sec-in-IE6-on-2...
- http://danieltao.com/lazy.js/
In Laws of Performant SoftwareHe also has a nice page on his github with lots of info on making stuff fast on node.
https://github.com/petkaantonov/bluebird/wiki/Optimization-k...
In Three JavaScript performance fundamentals that make Bluebird fastCheck out the Bluebird benchmarks [0], or you can easily try it for yourself - create a simple web server which does some makework async task, like stating a bunch of files, then benchmark with ab or something better.
[0] https://github.com/petkaantonov/bluebird/blob/master/docs/do...
In Async and AwaitpromisifyAll is _blazing_ fast because it does this: https://github.com/petkaantonov/bluebird/blob/master/src/pro...
It builds a function dynamically and then compiles it and lets the JIT optimize it - it incurs very little overhead.
This is impossible if your only tool is the promise constructor. That said - there are packages that do this without bluebird - like thenify.
Also note - you can use bluebird for promisification and native promises for other stuff if you'd like and it'd work seamlessly as bluebird passes the Promises/A+ test suite.
In Async and AwaitShowing the 15 most recent of 87 sources. Enable JavaScript to search and browse every indexed mention.