-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
2000x slower drawImage #867
Comments
In the comparison of the three, the time consumption of drawImage differs the most, with nap-rs/canvas taking as long as 3 seconds. I suspect that the synchronous method is causing "queueing" in the main process. |
@Brooooooklyn Are you able to publish a new version so I can test? or is there a way I can test without a new version. thanks |
A big improvement. Thank you NAPI Canvas Average: 10.68 ms, Min: 8.92 ms, Max: 20.96 ms |
@gc @Brooooooklyn
this is my global env variable The memory hasn't been released for a long time, even though I regularly execute |
drawImage appears to be 2000x slower than other canvas libraries.
The benchmark is drawing lots of parts of a big image (i.e sprites/spritesheets)
NAPI Canvas Average: 2413.62 ms, Min: 2338.18 ms, Max: 2525.64 ms
Node Canvas Average: 0.69 ms, Min: 0.58 ms, Max: 1.05 ms
Skia Canvas Average: 0.72 ms, Min: 0.52 ms, Max: 1.40 ms
Benchmark code https://github.com/gc/canvas-drawimage-benchmark
The text was updated successfully, but these errors were encountered: