-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
One anomaly run should not cause a perf alert. #27838
Comments
this is a bug in alerting. 1 anomaly at the end of the observation should not result in an alert. |
Performance change found in the For more information on how to triage the alerts, please look at
|
Performance change found in the
test:
pytorch_image_classification_benchmarks-resnet101-mean_load_model_latency_milli_secs
for the metric:mean_load_model_latency_milli_secs
.For more information on how to triage the alerts, please look at
Triage performance alert issues
section of the README.Test description:
Pytorch image classification on 50k images of size 224 x 224 with resnet 101. Test link -beam/.test-infra/jenkins/job_InferenceBenchmarkTests_Python.groovy
Line 34 in 42d0a6e
The text was updated successfully, but these errors were encountered: