-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Major slow down in kubernetes.io build time over the past 1-2 years. #8918
Comments
IMO one of the best ways to pinpoint what may be causing the issue(s) is running with |
Thanks for the tip @braderhart! Everything w/ cumulative duration over 1s:
I'll try to dig a bit more into making sense out of this. Let me know if anything jumps out. |
Looks like we might be able to leverage partialcached function on a few things:
Edit: Spoke too soon, looks like we might already be leveraging it.
|
This discussion is better suited for the forum (https://discourse.gohugo.io/). Having said that... https://www.docsy.dev/docs/adding-content/navigation/
After setting |
Good call out, you're right, I'll move to discuss. Thanks for the tip. Closing the issue now but will test / record / link any solution back for posteriority. |
Last note, this is the area you'll want to focus for now. The cumulative duration appears to include the time it takes to generate the previous templates, so you'll want to focus on these for now:
Last, it appears this is what is taking up the most time, but it could be
|
I need to validate the functionality of the site but WOW did that improve things. Thanks @jmooring
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What version of Hugo are you using (
hugo version
)?Sorry, this issue is a bit subjective but I'll do my best to build a case. I joined SIG Docs in 2018 and hugo built fast (that would probably be around release 1.11 / hugo version 0.40.3). Today it takes ~1:23m
Since then, we've added many more localizations, increased content, changed themes, and began relying more on data to generate pages such as k8s.io/releases/. The slowness in hugo wasn't overnight, it gradually became slower and slower. I'm trying now to decipher how we can correct the build times or improve them but grasping for straws. It doesn't seem like we're building a site that huge (~11,000 static files and ~4,500 pages).
It's also worth noting that the build consumes a TON of resources, mainly CPU (occasionally crashing my 4x4 VM due to OOM).
Any suggestions? I cross opened an issue on k/website too: kubernetes/website#29429
The text was updated successfully, but these errors were encountered: