Github user twilmes commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/274#issuecomment-200309448
I had done it like that so you could switch back and forth between
branches, run benchmarks, and the results would be persistent for comparison
purposes without copying them out of `target`. Having said that, I'm just
using the benchmark class name as the name of the file so these would get
overwritten every run anyway. I could update that naming to include an
incrementing number in the file name. I'm not opposed to putting them under
target, though. I'd imagine the usual performance tuning cycle may go
something like iterate on perf improvements in your branch, running benchmarks
as you make updates. Then commit, switch back to master or latest stable, run
benchmarks again, and note how much of an improvement you made.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
