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

Print perf context for all benchmarks if enabled #10396

Closed

Conversation

riversand963
Copy link
Contributor

Summary:
If user runs db_bench with -perf_level=2 or higher, db_bench should
print perf context after each of all benchmarks.

Or make -perf_level a per-benchmark switch.

Test Plan:
./db_bench -benchmarks=fillseq,readseq -perf_level=2

Summary:
If user runs `db_bench` with `-perf_level=2` or higher, db_bench should
print perf context after each of all benchmarks.

Or make `-perf_level` a per-benchmark switch.

Test Plan:
./db_bench -benchmarks=fillseq,readseq -perf_level=2
@riversand963
Copy link
Contributor Author

Not sure if this behavior is ok with you, cc @mdcallag

@facebook-github-bot
Copy link
Contributor

@riversand963 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@riversand963 riversand963 requested a review from ajkr July 21, 2022 03:31
Summary:
In db_stress, we have '-progress_reports' that controls whether the
process prints finished ops periodically to stdout. We can have the same
knob for db_bench, which can be handy when redirecting the output of
db_bench to files.

Test Plan:
./db_bench -benchmarks=fillseq -progress_reprots=false
./db_bench -benchmarks=fillseq

The first command disables progress reporting, while the second enables.
@facebook-github-bot
Copy link
Contributor

@riversand963 has updated the pull request. You must reimport the pull request before landing.

@facebook-github-bot
Copy link
Contributor

@riversand963 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

Copy link
Contributor

@ajkr ajkr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@riversand963 riversand963 deleted the db_bench-print-perf-context branch July 22, 2022 17:23
@riversand963
Copy link
Contributor Author

Thanks @ajkr for the review!

@mdcallag
Copy link
Contributor

Not sure if this behavior is ok with you, cc @mdcallag

Ugh, sorry for missing this. Thanks for the improvement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants