Update gaze to the latest version #412

jifeon · 2015-02-25T15:40:05Z

Hi, thank you for the great lib.

I have a performance issue on OS X. Here I read that [email protected] has better support for OS X, I updated gaze and it solved my problem. So I suggest to update it in the package.json file. Are there any reasons to stay on "^0.5.1"?

shama · 2015-02-25T18:00:42Z

[email protected] to [email protected] switched to native bindings. It has many perf fixes but at a cost. Users are required to build the native addon and for Windows users at Grunt's scale, bumping to [email protected] will lead to a lot of issues as building addons isn't easy for them.

So the path forward is this comment in another bump gaze PR: #408 (comment)

jifeon · 2015-02-25T18:42:03Z

Ok, but maybe workaround (manually installing fresh gaze for OS X users) should be mentioned somewhere in readme. I have been spent for hours trying to find out where is the problem. And the only solution I found is increasing some interval to 5007 😕 It was very strange :) because I can increase it to 5001 and have the same effect: need to wail approximately 5 sec before grunt starts to rebuild. So I think tiny note about it can save the time

shama · 2015-02-25T19:10:54Z

it's in the FAQ: https://github.com/gruntjs/grunt-contrib-watch#why-is-the-watch-devouring-all-my-memorycpu

jifeon · 2015-02-25T19:21:44Z

There is nothing about you can update gaze to 6.x manually for OS X users. Increasing the interval is not a good solution.

shama · 2015-02-25T22:00:39Z

Telling users to manually install a different version of a sub dependency isn't something we should advise people to do. If it works for you then fine.

If instructing users to bump the gaze version was a good solution, we'd just bump the dependency; not a note in the readme. But bumping gaze causes the tests to fail here as well as the previously mentioned Windows issues.

The road forward is fix the problems, not docs on hacks around them. Feel free to help me fix them too. :)

philipbulley · 2015-03-18T15:28:55Z

Not sure if this is useful to you, but will post anyway. I'm on Win7, I bumped gaze to 0.6.4. I have previously tackled the node-gyp vs Visual Studio C++ issues so it appears to have installed/built successfully. But running the watch task produces the following:

Running tasks: watch

Running "watch" task
Waiting...
Verifying property watch exists in config...OK
Verifying property watch.tyepscript.files exists in config...OK
Verifying property watch.scss.files exists in config...OK
Verifying property watch.markup.files exists in config...OK
Live reload server started on port: 35729
Fatal error: Cannot call method 'forEach' of null
Fatal error: Cannot call method 'forEach' of null
Fatal error: Cannot call method 'forEach' of null

drawveloper · 2015-03-19T13:35:05Z

@shama do you have any idea when gaze 0.6 will be released to npm?

shama · 2015-03-19T13:56:12Z

@firstdoit gaze 0.6 already has been published to npm. That isn't the issue.

drawveloper · 2015-03-19T14:20:15Z

Oops. I thought that only 0.5.1 was released.
https://www.npmjs.com/package/gaze

Ok then, thanks!

On Thu, Mar 19, 2015 at 10:56 AM Kyle Robinson Young <
[email protected]> wrote:

@firstdoit https://github.com/firstdoit gaze 0.6 already has been
published to npm. That isn't the issue.

—
Reply to this email directly or view it on GitHub
#412 (comment)
.

joshperry · 2015-04-01T23:30:53Z

+1 OSX user here, I have a few grunt processes running for API, web front-end, and open-id API. Each grunt was taking 5-6% CPU, >15% in aggregate, on a quad i7. I updated gaze to 0.6.1 directly in my node_modules and the CPU usage dropped to 0.3%. This sucks, but at least it keeps my MBP fan from spooling up.

Perhaps moving to shama/navelgazer (the layer that gazer uses for change notifications) would make sense, it has pre-built binaries so building for Windows users wouldn't be an issue. Does this plugin use any of the advanced globbing or other features of gaze?

shama · 2015-04-01T23:47:25Z

Sorry for all the confusion. Here is what needs to happen in order to upgrade:

Continue testing navelgazer and ensure it's stable
Finish integrating navelgazer into gaze (meaning all tests passing). Here is the branch where that is happening
Then integrate that next version of gaze into here and ensure all tests pass.
Publish a new version of grunt-contrib-watch.

Unfortunately I am the only one working on this atm and I don't have a lot of time lately (as my real job is getting close to launching our product). Hopefully I'll have more time to finish it all up later but would very much appreciate any help. Thanks!

joshperry · 2015-04-01T23:53:07Z

@shama Ah, sorry for the disconnect in my head between you working on both projects.

I'm in the middle of a crunch right now so I can't help either. I should have some time after our tradeshow in a couple weeks and I'll pop back to see if I can lend a hand.

freeall · 2015-04-30T17:13:39Z

@joshperry @shama Had the same issue with high cpu usage and came here. Tried to replace with gaze 0.6, but it only compiles on node 0.10. I couldn't get it to compile on 0.12 or iojs. Is this similar to what you've seen?

shama · 2015-04-30T17:20:03Z

@freeall Would you mind trying the navelgazer branch on gaze? That should compile with node v0.12 and io.js.

BTW, an alternative easier workaround for now that might reduce the CPU usage is setting a higher interval in the options.

freeall · 2015-04-30T17:38:05Z

@shama trying

freeall · 2015-04-30T17:44:03Z

Wow! It's much, much, much, much better! Went from idling >80% cpu (older macbook air) to ~0%. Using iojs.

Are you going to replace with this version+branch?

shama · 2015-04-30T22:48:38Z

@freeall That is the plan but I've been busy with work and distracted with other projects, so I haven't gotten to it yet. Currently there are a couple tests failing with that branch that need to get fixed and then we can integrate here.

freeall · 2015-05-04T08:48:58Z

@shama makes sense. Need any help?

I thought about it over the weekend, and it would be great to get updated for a little different reason. According to https://www.npmjs.com/package/grunt-contrib-watch there was >12k install over the last day. So it's running on a high number of machines. If the module is updated to the new method all these computers will now use less power to run, and although it may not mean a lot in the grand scheme of things this update could help the environment just a tiny bit.

I can try to look into this tonight if you're interested.

shama · 2015-05-04T15:44:39Z

@freeall Sure! Help is always welcomed. Thanks!

NickMele · 2015-06-15T16:56:01Z

@shama What is the status of this? I see your last comment mentions that you may need help with this. Have you gotten anywhere, or is anyone looking into getting this working?

shama · 2015-06-15T18:33:27Z

@NickMele The status is the same. I'll be sure to update the issue if the status has changed.

joshperry · 2015-09-30T00:23:58Z

@shama have some time to work on this. Question, if this is a good place to talk.

In the multipleInstances test, it is set up to expect a deterministic ordering of events from the two instances. Is this determinism something that gaze guarantees or can I fix the test to be order independent?

shama · 2015-09-30T00:47:50Z

Is this determinism something that gaze guarantees or can I fix the test to be order independent?

Feel free to fix the test to be order independent. Thanks!

joshperry · 2015-10-02T01:34:18Z

Hey guys, I spent some time yesterday finishing up navelgazer, integrating it with gaze on the shama/gaze#navelgazer branch, and getting all of their respective tests to pass.

My current project has two services that I run while doing dev work and usually accounts for around 20% CPU utilization. I worked with the new code today and it seems to be functioning correctly and has relieved my CPU immensely.

I installed this build on only one of the services and this is what they looked like after a handful of hours working:

👍

freeall · 2015-10-02T07:06:39Z

👍

shama · 2015-10-05T00:04:54Z

🤘 🤘 🤘

phallstrom · 2016-01-20T20:16:13Z

Wonder what the status of this is? Only watching a few files, but it's polling constantly.

shama · 2016-03-12T20:56:02Z

Fixed with e1b888f

Update gaze to the latest version

65d5802

jifeon mentioned this pull request Feb 25, 2015

High CPU usage #35

Closed

vladikoff mentioned this pull request May 7, 2015

Upgrade to newer gaze #435

Closed

joshperry mentioned this pull request Sep 30, 2015

Initial changes for node 4 support shama/navelgazer#10

Merged

ntwb mentioned this pull request Jan 1, 2016

Updated dependencies #483

Merged

shama closed this Mar 12, 2016

Update gaze to the latest version #412

Update gaze to the latest version #412

Uh oh!

Conversation

jifeon commented Feb 25, 2015

Uh oh!

shama commented Feb 25, 2015

Uh oh!

jifeon commented Feb 25, 2015

Uh oh!

shama commented Feb 25, 2015

Uh oh!

jifeon commented Feb 25, 2015

Uh oh!

shama commented Feb 25, 2015

Uh oh!

philipbulley commented Mar 18, 2015

Uh oh!

drawveloper commented Mar 19, 2015

Uh oh!

shama commented Mar 19, 2015

Uh oh!

drawveloper commented Mar 19, 2015

Uh oh!

joshperry commented Apr 1, 2015

Uh oh!

shama commented Apr 1, 2015

Uh oh!

joshperry commented Apr 1, 2015

Uh oh!

freeall commented Apr 30, 2015

Uh oh!

shama commented Apr 30, 2015

Uh oh!

freeall commented Apr 30, 2015

Uh oh!

freeall commented Apr 30, 2015

Uh oh!

shama commented Apr 30, 2015

Uh oh!

freeall commented May 4, 2015

Uh oh!

shama commented May 4, 2015

Uh oh!

NickMele commented Jun 15, 2015

Uh oh!

shama commented Jun 15, 2015

Uh oh!

joshperry commented Sep 30, 2015

Uh oh!

shama commented Sep 30, 2015

Uh oh!

joshperry commented Oct 2, 2015

Uh oh!

freeall commented Oct 2, 2015

Uh oh!

shama commented Oct 5, 2015

Uh oh!

phallstrom commented Jan 20, 2016

Uh oh!

shama commented Mar 12, 2016

Uh oh!

Uh oh!