constant CPU usage on watch

[Vasiliy-Bondarenko]

i see constant CPU usage around 12% on quite small number of files. ~230 *.php files.
no files changing at that time, no other watchers, no action at all.

CPU: i7 2.2
Mac OS X 10.9.4
node -v
v0.10.30
gulp -v
[02:08:51] CLI version 3.8.7
[02:08:51] Local version 3.8.7

watcher:

gulp.task('default', function (){
    gulp.watch('_lara/app/**/*.php', ['codecept']);
})

[yocontra]

cc @shama

[shama]

Try increasing the interval. By default it is 100ms which for some environments hits the CPU usage:

gulp.task('default', function (){
    gulp.watch('_lara/app/**/*.php', { interval: 500 }, ['codecept']);
})

[Vasiliy-Bondarenko]

it helps quite well.
is it happens bacause of nodejs or some deep system-level stuff? aniviruses watch for all files on file system and have no problems :)

[shama]

I'm not sure. Two users with the apparent same environment, 100ms works for one but raises the CPU for the other. My guess is it's the hardware or how the disk is organized causing the stat calls to take longer.

The next version only uses native OS events. More comparable to how applications installed with admin privileges watch files, such as antivirus programs. There are a couple issues outstanding preventing the update though. Please follow this issue for updates: shama/gaze#137

[yocontra]

Merging into #651

[griiettner]

I Tried the solution posted by @shama, but it did not do any change on CPU usage for my mac very similar to @Vasiliy-Bondarenko

[pkyeck]

works for me on a i7 3.0GHz MBP. thanks for the tip.

[starikovs]

Ubuntu 14.04.1 LTS the same bug, 12% of cpu.
If I set "interval: 500", ~3% of cpu constantly.
Anyway, thanks for the tip!

[unphased]

Hey guys, so... CPU usage should be 0% because polling is wrong. Does anybody agree?

I mean, I would use slightly less strong phrasing if this is actually a point of contention. But I mean... this is 2015. There are filesystem APIs.