You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: