Live data from Hacker News

Watchman: Faster builds with large source trees

facebook.com

21–22 of 22 posts

Re: Watchman: Faster builds with large source trees

#21

I was just looking into inotify to reload nginx and various other services on conf changes. I guess I'll go with Watchman so I don't have to write a series of shell scripts. I considered guard ( https://github.com/guard/guard ) and Nodemon ( https://github.com/remy/nodemon ), but Watchman has less dependencies (doesn't require Ruby/Node). There's also Supervisor (Python) ( http://supervisord.org/ ), but I think that…

Not directly applicable but if you are using Salt to manage your servers you set it up to restart a service when certain files change with the watch requisite [1].

[1] - http://docs.saltstack.com/ref/states/requisites.html#require...

Re: Watchman: Faster builds with large source trees

#22
post #9

If I'm reading that graph right, the red line is at 10kmsec, i.e. 10 seconds? Incremental build times are near and dear to my heart; I spent a lot of time making the Chrome incremental build fast, resulting in this tool: http://martine.github.io/ninja/ . In developing Ninja I was surprised to discover that Linux stat() with a warm disk cache is very fast -- well under 100ms to stat the ~40k source files Chrome uses i…

Ninja is awesome
Post reply on HN