Replies: 2 comments
-
Here is a link to my benchmark code: And the calls in: Have the same call count / instructions as the Clipper1 lib as seen here: |
Beta Was this translation helpful? Give feedback.
-
I ended up figuring out the culprit - I was comparing double operations with in64 operations, internally Clipper2 transforms doubles to ints so it was doing an additional transformation. These are my new results:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone,
I'm working on porting Clipper2 to WebAssembly and aiming to unlock its full potential. While Clipper2 should ideally perform at least 30% faster than Clipper1, my current benchmarks in a WASM environment are not reflecting this expected improvement.
My build process:
C libs:
WASM:
WASM Benchmark results:
Clipper1: 2901 ms
Clipper2: 2988 ms
C Benchmark results:
Clipper1: 1058 ms
Clipper2: 761 ms
Encountered Issue
Despite the theoretical performance improvements in Clipper2, my WASM port is not outperforming the existing Clipper1 port. The native C benchmarks show the expected performance gain, but this isn't translating into WASM.
Request for Community Input
I'm looking for suggestions on:
Any feedback or collaborative ideas would be greatly appreciated. Here's the link to my project for reference: https://github.com/ErikSom/Clipper2-WASM/.
Thank you all in advance for your help!
Beta Was this translation helpful? Give feedback.
All reactions