@jp/wayne- Thanks for the tests. Speed is not expected to be noticeably different unless the board has overlapping holes. Then poly2tri cannot cache the polygon and we triangulate using whatever routine the user's OpenGL driver implements. Since the OpenGL routine runs on a single processor and re-runs each time the zone is highlighted, the speed difference is primarily visible there. This is related to https://bugs.launchpad.net/kicad/+bug/1745050
and https://bugs.launchpad.net/kicad/+bug/1780130
@jp/wayne- Thanks for the tests. Speed is not expected to be noticeably different unless the board has overlapping holes. Then poly2tri cannot cache the polygon and we triangulate using whatever routine the user's OpenGL driver implements. Since the OpenGL routine runs on a single processor and re-runs each time the zone is highlighted, the speed difference is primarily visible there. This is related to /bugs.launchpad .net/kicad/ +bug/1745050 /bugs.launchpad .net/kicad/ +bug/1780130
https:/
and
https:/