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

[Feature Request] Include memory consumption in benchmark results #23

Open
advancedxy opened this issue Sep 21, 2016 · 2 comments
Open

Comments

@advancedxy
Copy link

Hi, some codec's high compression level may consume a a lot of memory. Is it possible to include memory consumption in benchmark results?

Also, -z means compression time instead of speed. The benchmark process can be interrupted by other processes, is it possible to include cpu time, which better indicates cpu consumption?

@inikep
Copy link
Owner

inikep commented Sep 26, 2016

Hi, these are good ideas.

The memory consumption is hard to do as each compressor uses it's own memory allocation which needs to be tracked.

@tansy
Copy link
Collaborator

tansy commented May 1, 2019

Maybe measure whole program usage before and during run of a the codec and simply subtract? I know it's simple, to not say primitive but this way you get approximate value of memory usage without knowledge of the running codec.

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

No branches or pull requests

3 participants