Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

if there are more than 100 files, it will cost 10sec !!! #147

Closed
tokki opened this issue Jun 6, 2013 · 1 comment
Closed

if there are more than 100 files, it will cost 10sec !!! #147

tokki opened this issue Jun 6, 2013 · 1 comment

Comments

@tokki
Copy link

tokki commented Jun 6, 2013

start roots watch

if i edit index.jade ,all the files (styl,jade)will be compile once, if there are more than 100files in my project, it will cost more than 10sec in my computer.

can we make it just compile index.jade, keep the other.(i think we should keep the file which is not change)

@jescalan
Copy link
Owner

jescalan commented Jun 6, 2013

Hey @tokki - you are right, if you're recompiling a large number of big files it will take longer. When you are using roots watch, as long as the file is not ignored, it should only compile that single changed file which will speed it up. But I am acutely aware that if you have a gigantic project, roots does not perform at optimum possible levels.

The reason I can't have it just compile the single file that you changed every time is because many times files have dependencies. For example, you might have a partial that's included on your index page - if you change the partial, the index page would have to be recompiled. Being able to detect what depends on what like this requires a sort of asset graph, which is something I will be working on and integrating into roots in the future. This is a large and difficult project though, so it will take a bit.

For now, I would assume that if you have an absolutely gigantic project that has to compile often, roots might not be the best option yet.

The other possibility is that you have a lot of files that never change - in this case it's easy to ignore them and drop them back in later. Just use the ignores in app.coffee to make this happen.

Ref #149

@jescalan jescalan closed this as completed Jun 6, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants