Skip to content

Generating this site takes an alarming amount of resources. #29429

Closed

Description

@jimangel

Look into evaluating how we can make building the site take less memory / cpu.

Problem

As k/website has grown, it went from a small hugo build to what it is today (a large, memory and file hungry build).

This is all good though, it means we are adding content and localizations.

Solution

Look into ways to reduce build time. A few options come to mind:

  • Can we remove a large chunk of unused content?
  • Can we build only a small subset of docs (easily and portable to the various localizations)?
  • Are there any optimizations in hugo itself?

There should be a way to reduce the amount of resources required to build k/website. Considering there isn't a clear solution, I won't mark as good-first-issue.

/sig docs
/triage accepted

Activity

  1. added
    kind/featureCategorizes issue or PR as related to a new feature.
    on Aug 17, 2021
  2. added
    sig/docsCategorizes an issue or PR as relevant to SIG Docs.
    triage/acceptedIndicates an issue or PR is ready to be actively worked on.
    on Aug 17, 2021
  3. sftim commented on Aug 17, 2021

    @sftim
    Contributor

    Idea: run the build localization-by-localization. I don't know if Hugo supports this but if it might let us run 14 shorter builds (potentially in parallel) rather than 1 long one.

    Idea: look for image resize options at build time. If reasonable to do so, replace the source image with what it gets resized to.

  4. sftim commented on Aug 17, 2021

    @sftim
    Contributor

    This might be an area where we could look for resources from CNCF to help with it - especially if the fix is applicable across multiple CNCF projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.sig/docsCategorizes an issue or PR as relevant to SIG Docs.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions