Polling slower than LiveReload.app?

[bltpc]

Hi,
I am working on a small static website assembled with gulp and served with gulp-webserver during development. Overall it's working fine, however it seems that live reload via gulp-webserver is somewhat slower to reload as compared to the liveReload.app (all of this on OS X 10.10)

I did not do hard measurements, but it's in the range of 1-2 seconds slower after doing e.g. a touch index.html in the root of the build directory. Not critical, but faster is always good.

Is there an explanation for this or better a fix, can the polling frequency be sped up? At this point I have <25 files watched, so would not expect it to be due to the size of the file tree.

[lion-man44]

I think as a slow reload than I even gulp-connect.

Is there a reload log that has been output by gulp-connect?

[16:55:40] Starting 'reload'...
[16:55:40] Finished 'reload' after 5.36 ms

[tomatau]

I have 2 files being watched and simply changing a string in a static html file takes over a second for a reload - seems very slow

[davidgengenbach]

#92
You could set the polling interval in the watchOptions - see pull request!

The default interval is high (~5s): https://nodejs.org/docs/latest/api/fs.html#fs_fs_watchfile_filename_options_listener

[kirillgroshkov]

+1

[maxim-danilov]

I trying https://github.com/hiddentao/gulp-server-livereload It seems that it works faster.