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
Jekyll build takes minutes to complete #228
Comments
Please provide a list of your gems. |
Here it is: Gemfile:
Gemfile.lock
|
That's exactly what I was looking to spot. Your problem is probably bootstrap-sass. This is a known issue I haven't decided if I want to fix or not (I probably will end up fixing it.) I've known about for a while, and something I had assumed that Sprockets 3 would handle, but actually, Sprockets doesn't cache that resource because it's imported by SASS. I know Rails works around it in their Sprockets by adding their own importer, something I will end up having to do but I just haven't had time to add it. It's not because your cache is being deleted (and if it were that would be a Sprockets bug... we ignore .asset-cache on your behalf along with other folders we use and deem need to be ignored so you can remove that from your exclude list entirely. |
@envygeeks - Thanks for the clarification. I will try to see how it works without bootstrap-sass. And I will be happy to test it when a fix is applied. |
Ok, same goes after removing bootstrap-sass gem.
Gemfile.lock
|
At this time my deduction is that maybe Jekyll is removing I need to consider looking into and adding proof tests to ensure that is not the case, and that bootstrap is the problem. If you feel these are not the issue you will need to provide more diagnostic relevance since my deductions are based on the short-falls I know in both systems and they line up perfectly and since you cannot provide source and won't take the time to provide replication I'm immediately siding with Occam and going with what I know are known problems. Without something to replicate this problem with that can demonstrate it, I cannot step into a context in both Jekyll and Jekyll Assets and see where the problem is. I'll be chasing the golden goose. So unless you can help me replicate it with source or example source that doesn't use your source I'll resolve the problems I know can cause this problem like Occam suggested. Sorry. |
I can confirm this. Switching from 1.x to 2.x (and no other changes at all) almost doubled our build time (from ~30s to ~60s). Will try to debug this and hopefully find a fix. |
Ok I think we know what the problem is.. will submit a PR within the next week or two. |
hey @fw42 wondering if you had any news or if you could point me in the right direction on this? We are about to let loose 2.2 in the next few days so it would be nice to get this fix in there! |
@envygeeks, sorry, we got distracted, I have a working fix, just need to polish it up. Will try to get something PRed within the next week. Can you wait that long with the release? |
@fw42 I can, I'll just cut a beta release for people who use RubyGems and had open tickets and your fix can go into the final release. |
So excited for this. 👍 |
For some reason, after migrating to Jekyll 3.0 (and Jekyll Assets 2), site build takes way longer than it was before the migration (from ~10 seconds to ~300 seconds).
I've already opened Jekyll Core's issue #4297, and seems like it's a Jekyll Assets issue.
Any help would be highly appreciated.
Thanks!
The text was updated successfully, but these errors were encountered: