Changes between Initial Version and Version 1 of Ticket #44241
- Timestamp:
- 05/26/2018 10:17:45 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #44241 – Description
initial v1 1 `grunt watch` appears to use around 40% of my CPU when sitting idle. By default, [ grunt-contrib-watch https://github.com/gruntjs/grunt-contrib-watch] uses a 100ms interval. Several of the groups in our `_watch` config specify an interval of 2 seconds, but others defer to the default.1 `grunt watch` appears to use around 40% of my CPU when sitting idle. By default, [https://github.com/gruntjs/grunt-contrib-watch grunt-contrib-watch] uses a 100ms interval. Several of the groups in our `_watch` config specify an interval of 2 seconds, but others defer to the default. 2 2 3 3 In my local environment (non-VM), if I add `options: { interval: 2000 }` to the config, colors, test, and phpunit groups, `grunt watch` CPU usage stays consistently within 2 to 5% at idle. 4 5 See [https://github.com/gruntjs/grunt-contrib-watch/issues/429 this related discussion on the grunt-contrib-watch project ] 4 6 5 7 If I change all configurations to 1 second, `grunt watch` CPU usage stays at around 9%.