-
I was working on a simple benchmark to compare the WASM port of Clipper1 with the WASM port of Clipper2 and currently Clipper1 is outperforming Clipper2 slightly, here is my setup: These are my results:
Here clipper2 is slightly slower - and I'm still figuring out whether this is due compile differences, implementation differences or a difference in the actual lib. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Clipper1_vs_Clipper2_performance.zip I suspect the performance issues you're seeing with Clipper2 is related to your translation. Edit: I suggest that your 'benchmark' intersecting/unioning etc 2 overlapping circles really isn't a good test because despite the number of edges in each circle, there will only be 2 points of intersections. |
Beta Was this translation helpful? Give feedback.
-
@AngusJohnson I have figured it out and am finally seeing the improvements :) I was comparing IntersectD with an intersect64, there is the overhead of transforming the doubles to ints. The new results here:
|
Beta Was this translation helpful? Give feedback.
@AngusJohnson I have figured it out and am finally seeing the improvements :) I was comparing IntersectD with an intersect64, there is the overhead of transforming the doubles to ints. The new results here: