-
Notifications
You must be signed in to change notification settings - Fork 125
Slow to document package:fhir? #2436
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
Note: the package archive is larger than usual, maybe it is some operation related to that? |
It was slow, but completed on my machine. 223.5 seconds to initialize, and 245.9 seconds to document. Since this is pretty unusual I will set priority to P2 and see if there is a specific reason (other than this package being fairly large, 182 public libraries). |
Pretty long! Definitely one to keep an eye on when doing performance improvements; for example mustache changes :D |
@srawlins I was thinking the same thing :-) |
For perspective, the Flutter SDK, current leader for single biggest documentation job in the Dart ecosystem, initializes on the same machine in 154.3 seconds and documents in 445.4 seconds. |
The performance improvements in 0.38 helps things a little bit, but not as much as I expected. This may be because this package contains an extremely complex import-export graph and lots of shallow classes, which reduces the benefit of not rerendering sidebars. |
Added #2615 for more debug information on slow packages. |
Seems like dartdoc now completes the recent version of package:fhir |
Closing as obsolete. |
Original report: dart-lang/pub-dev#4261
To replicate:
fhir 0.0.11
from here.pub get
pub global run dartdoc --json .
There seems to be no update about the progress, but the CPU is fully saturated for 20+ minutes on my MacBook.
The text was updated successfully, but these errors were encountered: