mirror of
https://github.com/thorvg/thorvg.git
synced 2025-06-13 19:44:28 +00:00
c8bc0a91d9
Now, we have 2 points for asynchronous behaviors. 1. update shapes: Each shape update will be performed by async when you push shape to canvas. Meaning, if you have time gap between update and rendering in process main-loop, you can have a benefit by this. 2. rasterization by canvas: Canvas.draw() will be performed asynchnously until you call canvas.sync(); Meaing, if you can trigger tvg rendering eariler than composition time. You can have a benefit by this. If these 1, 2 points might not work for your program, You can just toggle off async by setting threads number zero at initialization. Or if you could apply either point of them for your program, It might be good for performance. But the best approach is to make both async properly. Though this might need to fine-grained tuning integration between your program & tvg, You could achieve the best peformance by parallelzing tasks as possible without any jobs delaying. Change-Id: I04f9a61ebb426fd897624f5b24c83841737e6b5b |
||
|---|---|---|
| .. | ||
| bindings | ||
| examples | ||
| lib | ||
| loaders | ||
| meson.build | ||