-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add culori to benchmark #2
Comments
I've added a culori benchmark inside Testing with input type: Random Sampling in P3 Gamut
Conversion OKLCH to P3 --
Culori: 52.53 ms
Ours: 17.28 ms
Speedup: 3.0x faster
Gamut Mapping OKLCH to P3 Gamut --
Culori: 84.81 ms
Ours: 16.56 ms
Speedup: 5.1x faster
Testing with input type: Random Sampling in OKLab L Planes
Conversion OKLCH to P3 --
Culori: 44.20 ms
Ours: 12.92 ms
Speedup: 3.4x faster
Gamut Mapping OKLCH to P3 Gamut --
Culori: 1592.35 ms
Ours: 23.39 ms
Speedup: 68.1x faster
Testing with input type: Random Sampling in OKLab L Planes (Fixed Cusp)
Conversion OKLCH to P3 --
Culori: 46.21 ms
Ours: 12.98 ms
Speedup: 3.6x faster
Gamut Mapping OKLCH to P3 Gamut --
Culori: 1554.91 ms
Ours: 17.96 ms
Speedup: 86.6x faster I've also benchmarked the bundle size: it is smaller than Colorjs, coming in at ~43 kb (compare to ~3.5 kb for @texel/color). It should be noted that EDIT: The benchmarks had an error which should be fixed now; culori gamut mapping gets a little closer to @texel/color when input is already in-gamut. |
Amazing, thanks. I added task to try |
Thanks @mattdesl for including Culori in the benchmark (author here), and congrats on the project, the performance looks amazing on what is probably the most computationally-intensive color operation! We are using binary search for gamut mapping, which throws a wrench into the Big O, so I’m not surprised by the difference :-) I’ve added |
Hi. I am very interested in new color library for oklch.com.
We are using culori and if benchmark will show that your tool is faster I will think about switching.
Can you add it to benchmark?
The text was updated successfully, but these errors were encountered: