You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/04/19 21:25:00 UTC

[jira] [Commented] (GEODE-9175) Clean up the terminal output and log progress for benchmarks

    [ https://issues.apache.org/jira/browse/GEODE-9175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325323#comment-17325323 ] 

ASF GitHub Bot commented on GEODE-9175:
---------------------------------------

upthewaterspout opened a new pull request #147:
URL: https://github.com/apache/geode-benchmarks/pull/147


   Reducing the noise in the logging from our benchmark framework.
   
   Printing test log messages to stdout when running a benchmark, to watch the
   progress.
   
   Logging progress every 10 seconds in the yardstick task
   
   Reporting the throughput and latency every 10 seconds while running a
   benchmark. Each client currently reports it's own numbers.


-- 
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.

For queries about this service, please contact Infrastructure at:
users@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
>
> 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)