Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Watcher is quite slow to recognize changes after recent watcher updates. #2208

Open
mmase opened this issue Jan 9, 2018 · 9 comments
Open

Comments

@mmase
Copy link

mmase commented Jan 9, 2018

Watcher is quite slow to recognize changes after recent watcher updates. Perhaps this is isolated to large sass codebases. What used to be instant now takes 5 to 10 seconds. Once changes are recognized, compilation is normal/fast.

  • NPM version 5.6.0
  • Node version 8.9.4
  • Node Process
{ http_parser: '2.7.0',
  node: '8.9.4',
  v8: '6.1.534.50',
  uv: '1.15.0',
  zlib: '1.2.11',
  ares: '1.10.1-DEV',
  modules: '57',
  nghttp2: '1.25.0',
  openssl: '1.0.2n',
  icu: '59.1',
  unicode: '9.0',
  cldr: '31.0.1',
  tz: '2017b' }
  • Node Platform darwin
  • Node architecture x64
  • node-sass version
node-sass	4.7.2	(Wrapper)	[JavaScript]
libsass  	3.5.0.beta.2	(Sass Compiler)	[C/C++]
  • npm node-sass versions
be.net@0.0.0 /Users/mase/Code/behance/be.net
├── node-sass@4.7.2
@nschonni
Copy link
Contributor

nschonni commented Jan 9, 2018

What version are you comparing to when you found it fast?

@mmase
Copy link
Author

mmase commented Jan 10, 2018

@nschonni 4.5.2 is last one but maybe 4.7.1 or 4.7.0.

Here is a profile of what I am talking about. It looks like close is fired many, many times now. Appears to be an issue with gaze maybe. A bunch of us just noticed it quite recently though.

image

@weichenghsu
Copy link

I doubt it's due to the Mac OS high sierra version?

@mmase
Copy link
Author

mmase commented Feb 26, 2018 via email

@weichenghsu
Copy link

Thanks~ Any workaround solution so far?

@korve
Copy link

korve commented Mar 2, 2018

I have the same problem with macOS 10.13.3. The watcher is stuck at 100% CPU usage after updating a sass file that is watched by node-sass. It then takes around 20-30s to recognize the change.

Last working version for me is node-sass 4.5.3

$ node --version
v9.6.1
$ npm version
{ npm: '5.6.0',
  ares: '1.13.0',
  cldr: '32.0.1',
  http_parser: '2.7.0',
  icu: '60.2',
  modules: '59',
  napi: '2',
  nghttp2: '1.29.0',
  node: '9.6.1',
  openssl: '1.0.2n',
  tz: '2017c',
  unicode: '10.0',
  uv: '1.19.1',
  v8: '6.2.414.46-node.20',
  zlib: '1.2.11' }
$ node-sass --version
node-sass	4.7.2	(Wrapper)	[JavaScript]
libsass  	3.5.0.beta.2	(Sass Compiler)	[C/C++]

@weichenghsu
Copy link

weichenghsu commented Mar 9, 2018

Super slow on high sierra only. Also happens at sass (ruby gem) I believe they are sharing the same system library and the sys lib might be the bottleneck.

node --version && npm --version (git)-[develop]
v9.5.0
5.6.0

@evelant
Copy link

evelant commented Aug 9, 2018

Also seeing 100% cpu use on Mac OS 10.13.6. Reverting to node-sass v4.5.3 resolves it.

@idiazroncero
Copy link

I'm also experiencing this issue, node-sass is at 4.12

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants