Skip to content

Conversation

@JulianKnodt
Copy link
Contributor

@JulianKnodt JulianKnodt commented Jul 27, 2021

There were no benchmarks for neuquant, and it's worthwhile to figure out what consumes time when
quantizing the colors. This creates two benchmarks, one for the creation of the quantization,
and one for the searching of the nearest color. It tests on a static image which is mostly green
and red.

Current output:

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s


running 2 tests
test bench_map_pixel ... bench:          50 ns/iter (+/- 21)
test bench_new_nq    ... bench:   6,385,162 ns/iter (+/- 1,435,915)

test result: ok. 0 passed; 0 failed; 0 ignored; 2 measured; 0 filtered out; finished in 10.26s

Updates #12

Let me know what the best method would be for getting it to compile on old systems, target-features, a build script, etc.

@JulianKnodt JulianKnodt force-pushed the benchmark branch 4 times, most recently from 19443e7 to f59b547 Compare July 27, 2021 19:59
There were no benchmarks for neuquant, and it's worthwhile to figure out what consumes time when
quantizing the colors. This creates two benchmarks, one for the creation of the quantization,
and one for the searching of the nearest color. It tests on a static image which is mostly green
and red.
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

Successfully merging this pull request may close these issues.

1 participant