[
https://issues.apache.org/jira/browse/GEODE-9175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428480#comment-17428480
]
ASF GitHub Bot commented on GEODE-9175:
---------------------------------------
upthewaterspout opened a new pull request #157:
URL: https://github.com/apache/geode-benchmarks/pull/157
Changing a bunch of debug output to info level to reduce the amount of
noise the benchmark framework is printing out.
This is not the full scope of GEODE-9195, which also is asking to
print out progress as the test runs.
Splitting this work out from #147. I still need to investigate
the failure I saw with that PR and show that the progress logging has no
measurable performance impact. But removing these extra log
messages should get in as well.
I left in the logProgress method that allows the benchmark tasks to log
output to the gradle console if they want to, but we are not currently
logging anything until I clean up #147.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Clean up the terminal output and log progress for benchmarks
> ------------------------------------------------------------
>
> Key: GEODE-9175
> URL: https://issues.apache.org/jira/browse/GEODE-9175
> Project: Geode
> Issue Type: Improvement
> Components: benchmarks
> Reporter: Dan Smith
> Assignee: Dan Smith
> Priority: Major
> Labels: pull-request-available
>
> When developing a new benchmark with geode-benchmarks or testing out code
> changes interactively, it would be nice to for the geode-benchmarks to log
> the current throughput and latency numbers as the test is running, similar to
> the way YCSB does.
> This lets someone writing a new benchmark quickly eyeball if the performance
> has changed, or if their warm up time is too short or too long because the
> throughput fluctuates.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
