-
Notifications
You must be signed in to change notification settings - Fork 712
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
v0.26.0 increases RAM usage significantly #2607
Comments
Part of this is I apparently just forgot how packages mode works, and violated one of the requirements for it. TypeDoc 0.26 stores a files registry which is used to track what paths belong to... and I extended that with the ability to hold reflections, so relative paths to files would create links... the way I did that was by saving a // The combination of these two make up the registry
protected mediaToReflection = new Map<number, Reflection>();
protected mediaToPath = new Map<number, string>();
protected reflectionToPath = new Map<Reflection, string>();
protected pathToMedia = new Map<string, number>(); It's entirely possible there are other issues here too... still looking into it. It is possible to to run TypeDoc individually on each project, and then merge the results together, the typedoc-packages-example repo has an example of how to do this. |
I have a large monorepo https://github.com/yoursunny/NDNts that uses TypeDoc.
TypeDoc build steps in my monorepo
When using TypeDoc 0.25.13, the Node process running TypeDoc can run to completion using around 1.5 GB RAM.
After upgrading to TypeDoc 0.26.0, the Node process running TypeDoc needed to consume more than 7.3 GB RAM.
My system is Ubuntu 22.04, Node 20.12.2, TypeScript 5.4; I observed RAM usage with
htop
command.The significant RAM increase would cause difficulty in running such builds on GitHub Actions free tier, which has a RAM limit of 7.5 GB.
Is there some way to reduce RAM usage, or break the build into multiple stages and then combine them?
The text was updated successfully, but these errors were encountered: