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

consider moving to x/perf/cmd/perflock #3

Open
mvdan opened this issue Jan 4, 2019 · 1 comment
Open

consider moving to x/perf/cmd/perflock #3

mvdan opened this issue Jan 4, 2019 · 1 comment

Comments

@mvdan
Copy link

mvdan commented Jan 4, 2019

The average Go developer uses the same computer to develop Go that they use to talk to other people and browse the web. So it's very normal for CPU usage to fluctuate, even when one is working.

I personally think that for this reason, perflock is as important as https://godoc.org/golang.org/x/perf/cmd/benchstat, so it should likely live in the same repository. Advantages of doing so:

  • Easier to find, and more of an "official" tool
  • Part of the official repos, so it's easy to contribute to (including licensing, etc)
  • Improved bus factor :)

benchstat was similarly moved from https://github.com/rsc/benchstat, so I presume we could do the same here. Happy to help if any help is needed.

@mvdan
Copy link
Author

mvdan commented Jan 4, 2019

The "easier to find" would basically mean better documentation, which is golang/go#23471.

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

1 participant