-
Notifications
You must be signed in to change notification settings - Fork 1.7k
apidoc during build step is terribly slow #4579
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
Comments
Added this to the M1 milestone. |
When profiling apidoc, please check IO performance. We used to generate "dynamic" docs, which results in less bytes written to the file system. However, the downside is that it results in slower page loads. We now generate "static" docs, so our api.dartlang.org pages load much faster now. Also, what does "terribly slow" mean? |
As Lars said: " 20 minute is terribly slow :) In general I don't think we want to run tools on the debug VM. |
This comment was originally written by [email protected] Does anyone want to speak in favor of having build.py run apidoc on the checked-mode VM? My understanding is that
|
I'm OK with disabling the apidoc build step in debug mode. |
Did this get resolved? I remember the VM guys tweaks some code that sped this up. cc @iposva-google. |
Some improvements have been made here, but there's still more to do for M2. cc @rakudrama. |
We don't do that anymore right, should this be closed |
Removed Area-Build label. |
Removed this from the 1.6 milestone. |
Removed Oldschool-Milestone-1.6 label. |
Added AssumedStale label. |
There are two parts to this:
The text was updated successfully, but these errors were encountered: