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

Create benchmark suite #7

Closed
shssoichiro opened this issue Feb 19, 2016 · 5 comments
Closed

Create benchmark suite #7

shssoichiro opened this issue Feb 19, 2016 · 5 comments
Labels
I-Minor Issues that would be nice to have fixed, but are the lowest priority L-Python

Comments

@shssoichiro
Copy link
Owner

I'd like to have some benchmarks to compare this with optipng. I'd like to compare compression, speed, and memory usage--cargo bench is probably out of the question, so maybe this can be done in Python or similar.

Ideally this would be reusable to help optimize oxipng as well. Maybe have the benchmarks run against oxipng only by default, and a flag to have it run the comparison benchmarks.

@shssoichiro shssoichiro added I-Minor Issues that would be nice to have fixed, but are the lowest priority L-Python labels Feb 19, 2016
@shssoichiro shssoichiro added I-Medium Issues that are breaking core functionality, but have a known workaround and removed I-Minor Issues that would be nice to have fixed, but are the lowest priority labels Mar 4, 2016
@SethDusek
Copy link
Contributor

Something like this? Note: It isn't complete yet

@shssoichiro
Copy link
Owner Author

Yes, something like that is a good start.

@SethDusek
Copy link
Contributor

Another alternative could be an openbenchmarking test, and it could get nice graphs and stuff both compared to optipng, and the improvement in oxipng over a period of months (see http://linuxbenchmarking.com/)

@shssoichiro
Copy link
Owner Author

Interesting. This does seem useful. Does it have the option to benchmark aspects other than the running time?

@shssoichiro shssoichiro added I-Minor Issues that would be nice to have fixed, but are the lowest priority and removed I-Medium Issues that are breaking core functionality, but have a known workaround labels Apr 4, 2016
@shssoichiro
Copy link
Owner Author

I've created a benchmark suite for cargo. It only tests the running time, and I'd still eventually like to benchmark memory usage, but I think this will suffice for now. It at least gives a baseline for optimizing performance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I-Minor Issues that would be nice to have fixed, but are the lowest priority L-Python
Projects
None yet
Development

No branches or pull requests

2 participants