-
Notifications
You must be signed in to change notification settings - Fork 644
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
Package validations can be made much quicker with a "queue-back" #7185
Comments
joelverhagen
added a commit
to NuGet/ServerCommon
that referenced
this issue
May 27, 2019
…ed as completed (#296) Progress on NuGet/NuGetGallery#7185
joelverhagen
added a commit
to NuGet/NuGet.Jobs
that referenced
this issue
May 28, 2019
joelverhagen
added a commit
to NuGet/ServerCommon
that referenced
this issue
May 30, 2019
…ed as completed (#296) Progress on NuGet/NuGetGallery#7185
joelverhagen
added a commit
to NuGet/NuGet.Jobs
that referenced
this issue
May 30, 2019
joelverhagen
added a commit
to NuGet/NuGet.Jobs
that referenced
this issue
May 30, 2019
joelverhagen
changed the title
Package validations can be made much quicker with a "queue-back"
[Queue-Back] Package validations can be made much quicker with a "queue-back"
Jun 3, 2019
joelverhagen
changed the title
[Queue-Back] Package validations can be made much quicker with a "queue-back"
Package validations can be made much quicker with a "queue-back"
Jun 3, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Downstream validators can queue back to orchestrator when they are done. This can save minutes. From testing on DEV, it can save on average roughly 2 minutes and 30 seconds per initial package validation.
Results
Over the past 7 days (4 days with queue-back, 3 days without queue-back), this is the improvement of validation times at a variety of percentiles. In short, we shaved off 2 minutes of validation time!
Snapshot on 9/24
This is the P95 validation time, per 6 hours over the past 7 days.
Snapshot on 10/4
Queries
The text was updated successfully, but these errors were encountered: