The URef migration as implemented in the initial PR for feat-uref-2 cannot be run in increments and it can potentially take a very long time to complete. We should test it for both correctness and performance with casper-db-utils and a mainnet snapshot and depending on how long it takes we might want to look into optimising that by finding a way to run it in increments, making it migrate records lazily or use some other optimisation.
The URef migration as implemented in the initial PR for feat-uref-2 cannot be run in increments and it can potentially take a very long time to complete. We should test it for both correctness and performance with casper-db-utils and a mainnet snapshot and depending on how long it takes we might want to look into optimising that by finding a way to run it in increments, making it migrate records lazily or use some other optimisation.