-
Notifications
You must be signed in to change notification settings - Fork 13
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
bench: more system data #47
Labels
Comments
These will be helpful: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
openbenchmarking.org does a good job of recording system specs as benchmark metadata. http://openbenchmarking.org/result/1405134-PL-AIOLAPTOP47
I'd like to do the same for our benchmarks. Either transliterate their code to python (if it's simple enough) or vendor the php.
https://gitorious.org/phoronix/phoronix-test-suite/source/master:pts-core/objects/phodevi/components
Then we'd try to get benchmarks from a particular machine (type) into separate folders. They'd be named either by a hash of the system data, or some more human-readable subset of the system data. I'd really like to get to a place where we can detect regressions on travis, at least when we hit previously-seen hardware.
The long-long-term goal would be some kind of benchmarking-helper library that we could use both in cheetah and other performance-sensitive projects.
The text was updated successfully, but these errors were encountered: