How to track and reduce hugo memory usage on build (getting OOM)

I have a site with 500k+ pages. Currently I use docsy. The last few months it keeps getting out of memory on build. I currently build on my desktop with 64 GB of RAM.

I tried to use the older version and the last successful build is with version 0.105

I suspect this is related to code embedded in pages (sorry I forgot what was my findings so I came to this hypothesis few months back).

My question is how to track /identify the memory usage so I can make improvement on the problematic part?

Thank you

1 Like

Have you already tested hugo --printMemoryUsage?

bep has been working on the “million page” release for some time, must be a hard nut to crack.

2 Likes

Im having same issues

This thread is from November 2023. The core of Hugo was reimplemented in February 2024. I’m not saying that this could not be an issue anymore, but it’s certainly not exactly what this thread started to be about.

I would start by tweaking the OS env variable HUGO_MEMORYLIMIT. It’s in gigabytes; if it’s not set, Hugo tries to set it based on the total system memory, which may or may not be too … eager.

But if this still is a problem, please create a new issue with more info. “I’m having the same issues” is not helpful.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.