Skip to content
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

Documentation performance. #403

Open
mikelittle opened this issue Aug 4, 2022 · 1 comment
Open

Documentation performance. #403

mikelittle opened this issue Aug 4, 2022 · 1 comment
Labels
developer advocacy Developer Advocacy related tasks should have Should be done, medium priority for now

Comments

@mikelittle
Copy link
Contributor

Within my local development environment it takes around 12 seconds to display the Developer docs documentation page.
On our infrastructure (altis.dev) it takes about 11 seconds.
On Github codespaces it takes less than 3 seconds.

My local environment is a M1 Macbook with 4CPUs and 7.9GB of memory allocated to Docker.
My codespaces environment it 4 cores and 8GB of memory.

I'd expect a similar performance from all environments.

I think we need to look at caching the documentation tree, so we don't have to parse every module directory and file, for every request.

@mikelittle mikelittle added the should have Should be done, medium priority for now label Aug 4, 2022
@johnbillion
Copy link
Member

I'm seeing even worse performance for the User Guides documentation. On my local-server environment (M1 Macbook Pro with all the resources you should need) it takes 28 seconds to generate, and almost all of that time is spent inside Parsedown.

@missjwo missjwo added the developer advocacy Developer Advocacy related tasks label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
developer advocacy Developer Advocacy related tasks should have Should be done, medium priority for now
Projects
None yet
Development

No branches or pull requests

3 participants