New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to Node 8.12 to address CPU usage problems related to fibers #10117
Comments
This should be handled in this PR: #10090 which looks like it should land in 1.7.1 |
node 8.12 has been released! https://nodejs.org/en/blog/release/v8.12.0/ |
You can start using Node 8.12.0 in the latest Meteor 1.7.1 release candidates! meteor update --release 1.7.1-rc.11 |
See also #10216, which is why we've reverted the upgrade for now. |
https://nodejs.org/en/blog/release/v8.12.0/ Closes #10117 and #10090. We will continue to monitor issue #10216.
In order to reflect what's been fixed in the Meteor 1.8.1 milestone so far, I'm going to close this issue now, though of course you'll need to run meteor update --release 1.8.1-beta.8 to get Node 8.14.0. |
Node has a bug fix related to performance with fibers, which is very important to Meteor. Without the fix applied, any Meteor process which creates a large number of fibers will become very slow; switching between fibers is O(n) in the peak number of concurrent fibers the process has ever contained.
The fix is present in Node 10.2.0 and later, and which will be in Node 8.12 as soon as they cut a release, which should be soon. Meteor is currently on Node 8.11, which is affected.
Node 8.12 release PR page: nodejs/node#21593
The text was updated successfully, but these errors were encountered: