Spanning-Tree Path Cost Long Method (32 bit path cost value enablement) Considerations?

Hi,

We're planning to enable the long method (32 bit value) for spanning-tree path cost across our switches, and I am curious if anyone has done this at a reasonably large scale before and what the implications of the change were. Did the spanning-tree process treat this as an event that required re-convergence (a topology change), or was it relatively seamless/low-impact and the path cost values started to reflect the 32 bit / long method shortly after this option was enabled?

Thanks!