This repository was archived by the owner on Sep 1, 2025. It is now read-only.
Conversation
Member
|
Any reason not to use built-in Go benchmarking (e.g.: https://dave.cheney.net/2013/06/30/how-to-write-benchmarks-in-go)? |
Contributor
Author
|
As I understood it that is targeted to benchmarking Go code, and assumes you can do a lot of go calls sort of without external effects and are interested in how long the go code takes to do stuff. It seems like a different purposes -- this is just go code being written to generate load on the backend, and then it is the backend being benchmarked; not this code. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Simple crude benchmark program