-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
Higher CPU load than webpack-dev-server? #40
Comments
Same here, although CPU usage at about 40%, not as high as 100%, but still not < 5%.
|
... It's all because of the webpack watcher. |
same problem, with a similar configuration of @avioli |
I have about 100% on my CPU, memory is growing too. I tried to profile it with |
propably the native module for the watcher is not installed, so the watcher switch to polling mode, which is cpu intensive. Try to install the fsevents module for OS X, or increase the polling frequency. |
This is a counterintuitive solution, as chokidar does list fsevents in |
Closing this issue because it's not related to this middleware. watchpack is related. |
Thanks @michaek !!! Work proxy was freezing the install of fsevents and I was cancelling it, thinking nothing bad was happening |
@michaek Worked for me as-well, thanks. |
I've had the same problem since I updated node, |
amazing. thank you, @michaek! |
I was playing around with making my own asset server (to replace webpack-dev-server) and noticed that it causes a huge spike in CPU load (~100% with fans spinning) compared to the dev server (~3%) when both are just idling.
These are just measured using Activity Monitor on a 10.9.5 Macbook Pro (quad core i7, 16GB RAM). Don't think the specs of the machine are super relevant, but there's definitely a noticeable difference when switching between the two and wanted to see if anyone had input.
The text was updated successfully, but these errors were encountered: