3 ms·
Any performance numbers? When processing millions of pixels, and deciding to tradeoff handwritten vector assembly for nice Go, it's valuable to know exactly ho
by londons_explore 7y ago
Any performance numbers?
When processing millions of pixels, and deciding to tradeoff handwritten vector assembly for nice Go, it's valuable to know exactly how much performance we are losing in return.
- amzans 7y agoHey! I just added some basic benchmark numbers in case it's useful: https://raw.githubusercontent.com/anthonynsimon/bild/master/benchmarks.txt https://raw.githubusercontent.com/anthonynsimon/bild/master/... This will hopefully also make performance regressions over time a bit more visible.
- okigan 7y agomaybe a good start, seems this compares rotation for 90 degree angles and resizes of natural multiples (2,3,4..) if so that's not enough to consider for production consideration. Check out benchmark suite, seems more comprehensive: https://github.com/jcupitt/libvips/wiki/Speed-and-memory-use https://github.com/jcupitt/libvips/wiki/Speed-and-memory-use