Skip to content
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

Document how to compare benchmarks from two different source repositories #14

Open
gasche opened this issue Aug 22, 2015 · 2 comments
Open

Comments

@gasche
Copy link

gasche commented Aug 22, 2015

To avoid having to make world.opt each time I switch between the pristine branch and the optimization-enabled branch, I often use two distinct copies of the source directories, one in each branch (with two shells open, one in each corresponding switch).

The operf-micro webpage seems to assume that the two test runs to compare have been run from the same directory, and thus share the same .operf directory. It does not indicate how to compare test across .operf directories, or how to specify at init/build time another place to place or find .operf than the current directory.

Would it be possible to document the workflow where the two compiler versions to compare are located under distinct repository paths?

@chambart
Copy link
Member

It is the case. There are two .operf directories. When you run some benchmarks, the compilation happens in a local one, and the results are stored in $(HOME)/.operf/micro/. When you run operf-micro compare it compares all the results that are stored in your home directory. This command does not need to run where you ran the benchmarks.

It effectively does not seem obvious from the documentation, I will try to improve that.

@gasche
Copy link
Author

gasche commented Aug 24, 2015

Thanks for the clarification. Maybe the compiler-local .operf directory could be named .operf-build to avoid the confusion?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants