-
Notifications
You must be signed in to change notification settings - Fork 85
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
Update benchmark results after migrating to AWS. #127
Update benchmark results after migrating to AWS. #127
Conversation
Thanks very much for running these Scott. Are the results deterministic within AWS? I.e. if a new instance is spun-up, do we at least get the exact same results across those cases? I would be less concerned in that case about any differences between these results and Oracle (e.g. the accuracy changes look equivocal). |
@nielsleadholm I'm rerunning benchmarks now, and I'll post an update when they're done. It'd be really nice to have a complete answer about reproducibility (i.e., rerun all benchmarks, including laptop). I think I can probably get this done in 2-3 hours with AWS. |
Reproducibility ReportSince we are on a new infrastructure and some results were different than on OCI, I ran the benchmarks a second time. Below are tables of both batches of runs. I'm happy to report that everything is identical except small variations in run times. Shorter Experiments with 10 ObjectsRun 1
Run 2
Longer Experiments with all 77 YCB ObjectsRun 1
Run 2
Unsupervised LearningRun 1
Run 2
Monty-Meets-WorldRun 1
Run 2
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for running those Scott.
Given the results are identical across the two AWS runs, I'm not concerned about issues with our seed fixing etc, and I assume that some of the other potential elements we discussed might explain the Oracle vs AWS differences. The accuracy changes between Oracle and AWS look equivocal to me so I think we should merge this and not spend 1 week+ chasing possible causes, i.e. given they haven't had a negative effect.
@vkakerbeck just tagging you to make sure you agree before we merge it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that makes sense. Thanks for updating those Scott and for making sure the new infrastructure still produces consistent results!
This PR updates benchmark results tables after migrating to AWS. No changes have been made to tbp.monty's core code since the last set of complete benchmarks was completed.