Version 2 of the EPoly extension runs much faster by storing intermediate information about the polys, rather than recalculating everything each time it gets called.
The downside of this is that it will not notice any changes that are made to the polys.
If the geometry of your polys might possibly change, e.g. by using enableEditing(), insertVertex() or deleteVertex(), then use version 1 of the EPoly extension.
Version 2 also uses more memory than version 1, to store the intermediate information.
The version 2 interface is identical to that of version 1 except that you copy the epoly2.js code into your own webspace and load it like:
This v2 example is identical to the v1 example except that it uses version 2 of the EPoly extension, and as you can see it runs considerably faster.