Add simple macros for the 4 session-benchmarking methods #9
Conversation
This file contains 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
added 3 commits
May 25, 2013 11:19
Signed-off-by: Nano <a>
…nchmark Target Signed-off-by: Nano <a>
…e the default Class/Method helper string Signed-off-by: Nano <a>
|
Still need to test this pull request, hold off on accepting. |
Signed-off-by: Nano <a>
|
There we go. That last commit adds the feature you're looking for, optional |
MattesGroeger
pushed a commit
that referenced
this pull request
Jan 17, 2014
Add simple macros for the 4 session-benchmarking methods
|
I just now saw your pull request by coincidence. I'm really sorry, for some reason I didn't get any notification. Great work, I'll merge it and create a new version asap! Thank you so much! I'm watching my own project now, hope I'll get notified next time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
stepmethod, it inserts a string with the Class and Method which is calling the macro.MGBenchStep()at the end of each method you want to track from, as that will tell you (assuming you're putting the method in most/all of your benchmarked methods) how long that method ran for.