MR: Pending <!-- NOTE: For context on MR heading, see: https://handbook.gitlab.com/handbook/engineering/devops/dev/create/remote-development/index.html#relationship-of-issues-to-mrs --> ## Description Following up on conversations [here](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/15148#note_2694101737), Handbook repo workspace running `hugo` command takes around 20 minutes to finish, and we would like to figure out ways for improving this. Furthermore, currently we configured using 10GB for Handbook repo workspace, as `hugo` command would event use all those 10GB while processing (after finished, memory usage back to around 5GB). This might worth improving as well. For reference, for Internal Handbook repo workspace, `hugo` command takes around 5 minutes to finish. https://gitlab.com/gitlab-com/content-sites/internal-handbook/-/merge_requests/7317#note_2693951626 <!-- TODO: What kind of issue is this? Please uncomment and include one of the following: /label ~"type::feature" /label ~"type::bug" /label ~"type::maintenance" --> <!-- OPTIONAL: Is this a feature/enhancement? - Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole. - Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality. --> <!-- OPTIONAL: Is this a bug? Please uncomment and include the following: - **Current behavior:** - **Expected behavior:** - **Steps to reproduce:** - **Additional information:** please include VSCode version, browser dev tool logs, etc that might be helpful to debug the issue! --> ## Acceptance criteria TODO: Fill out (required) - [ ] [Describe what must be achieved to complete this issue.] - [ ] [If applicable, please provide design specifications for this feature/enhancement.] - [ ] [If applicable, please list any technical requirements (performance, security, database, etc.)] ## Implementation plan TODO: Fill out or delete (optional) [Provide a high-level plan for implementation of this issue, including relevant technical and/or design details.] <!-- NOTE: Feel free to expand with more sections and headers as needed --> <!-- DO NOT TOUCH BELOW -->