-
-
Notifications
You must be signed in to change notification settings - Fork 636
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
Performance triage for JVM smoketest #13779
Comments
Opened #13787 and #13788 after an initial round of profiling. Because #13787 causes a fair amount of unnecessary IO, it will likely muddy actual profiling of the JVMs being launched... but that's probably the next step. The actual sandbox creation time (see #13787) isn't horrible, but that's likely because the repository we're testing with is fairly small. I'd also like to get a ballpark for how much total compilation time |
I've done some comparison here and... there is work to do! No surprise there, but fixing (at least) both of the above issues will be necessary to get to a better baseline. My very rough comparison involved:
|
Also obvious in here is that in macOS we're running afoul of EDIT: Yea, confirmed. And this also affects fetching artifacts with |
With the above two issues addressed, I did a bit of profiling of the JVMs for |
Before recommending that users use the new backend, we'd like to ensure that they get a good first impression. We should do a few days of performance triage to set a bar and identify potential problem areas to fix during M2.
The text was updated successfully, but these errors were encountered: