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

Support greedy / immediate result reporting #158

Open
nicholasjng opened this issue Nov 11, 2024 · 0 comments
Open

Support greedy / immediate result reporting #158

nicholasjng opened this issue Nov 11, 2024 · 0 comments

Comments

@nicholasjng
Copy link
Collaborator

Instead of accumulating all results and then passing them off to a reporter like we do now, it is sometimes beneficial to report results as soon as they are available (for example in a console).

This has some implications:

  • First of all, the runner requires a slot for a BenchmarkReporter instance in its run method.
  • Secondly, for anything other than a console reporter, this could incur higher overhead than just a batched reporting, e.g. over a connection (HTTP, streaming, file writing). Maybe a "greedy" reporting could be a "batched reporting with batch size = 1" scenario.
  • Thirdly, for anything table-based, any non-static ("unbounded" in Google Dataflow lingo) data stream requires certain parameters up-front for correct rendering (e.g. max column width). These either have to be inferred or set upfront by some heuristic.
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