Performance degrades with number of holes

[Kartiku]

Is this a known issue with the ear clipping algorithm? At first I saw poor performance due to all the memory allocations from the object pool. A proper object pool with a free list fixes that. Replaced all std::vector with a simple vector allocating from an arena.

Now issue is excessive time spent in eliminateHoles. Going to try a monotone polygon decomposition algorithm instead as I read it handles holes better. Wanted to ask here in case I was doing something wrong. I'm on a slow android device with a lot of triangulation

[mourner]

A proper object pool with a free list fixes that. Replaced all std::vector with a simple vector allocating from an arena.

Sounds cool! Would you be open to submitting a PR with the optimization?

Now issue is excessive time spent in eliminateHoles. Going to try a monotone polygon decomposition algorithm instead as I read it handles holes better.

Yeah, this is a limitation of the algorithm. Monotone polygon decomposition would certainly be much better in that regard but that would mean basically rewriting the whole library from scratch. I'm still looking forward to trying this out in the future, but it's not a simple task so will take a while.

[jmaa4]

Yes

[jmaa4]

Yes