Closed darky closed 4 years ago
You are right, but Node 12 is fresh and not LTS. Lot of developer uses Node 8,10. I think we can drop only in ~v0.15
Node 12 will be LTS on 2019-10-XX. Will be very nice to see what the worker_threads will give to the project (when stable).
@icebob any news about this issue ?
No any news.
Node 10
Platform info:
==============
Windows_NT 6.1.7601 x64
Node.JS: 10.16.0
V8: 6.8.275.32-node.52
Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz × 8
Suite: Promise vs BlueBird vs Aigle vs await
√ No promise* 169,827,247 rps
√ ES6 Promise.resolve* 11,274,951 rps
√ ES6 new Promise* 11,719,615 rps
√ Bluebird Promise.resolve* 5,079,560 rps
√ Bluebird Promise.resolve + 5 x then* 1,105,344 rps
√ Bluebird new Promise* 7,109,401 rps
√ Aigle Promise.resolve* 12,550,337 rps
√ Aigle Promise.resolve + 5 x then* 3,226,746 rps
√ Aigle new Promise* 8,765,586 rps
√ await* 7,436,999 rps
√ Aigle Promise.resolve + 5 x then* 2,344,155 rps
Node 12
Platform info:
==============
Windows_NT 6.1.7601 x64
Node.JS: 12.14.1
V8: 7.7.299.13-node.16
Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz × 8
Suite: Promise vs BlueBird vs Aigle vs await
√ No promise* 146,991,741 rps
√ ES6 Promise.resolve* 12,495,557 rps
√ ES6 new Promise* 12,622,663 rps
√ Bluebird Promise.resolve* 5,342,943 rps
√ Bluebird Promise.resolve + 5 x then* 1,200,959 rps
√ Bluebird new Promise* 5,779,400 rps
√ Aigle Promise.resolve* 11,233,806 rps
√ Aigle Promise.resolve + 5 x then* 2,700,589 rps
√ Aigle new Promise* 6,978,561 rps
√ await* 9,412,061 rps
√ Aigle Promise.resolve + 5 x then* 3,090,279 rps
I think it's very straightforward. We should drop Bluebird because it's 2.5x slower than the native built-in Promise
Seems native promises (with async await) give impressive performance. Fresh benchmarks on node 12:
Maybe it's time to drop bluebird within of https://github.com/moleculerjs/moleculer/issues/433