We are in a way of migration utility data from Geometric Network to UN.
To have some understanding about data amounts and performance:
over 720k linear feature assets
over 110k kilometers of utilities
AssetPackage takes ~40min to load initial data + 3hrs to ImportAssociations (~500k records)
Initial data load and performance is acceptable, overall environment (Portal, Server, DB) performance is good.
But we see a performance issue during Enable Topology operation witch takes days, not hours. And performance degrades if subsequently Disable / Enable topology operations are performed, because _DIRTYAREAS, _ERRORS, etc. table data grows dramatically.
We understand that initial data has lots of validation errors generated. But we have some concern when thinking about such problem in production environment. For example to add extra asset types, rules, etc. means UN services will be unavailable during period of Enable Topology, while UN changes itself will take some minutes.
Is there any recommendations from ESRI regarding Enable Topology performance?
I have same observation, it takes ages to Enable Topology if there are too many errors. Iterative approach will be better. In my case, most of the errors were due to the missing rules, missing terminals, missing junctions and some snapping issues. "snap" tool and some simple model builder tools for setting terminals as well as adding junctions etc. fixed lot of errors. Enable Topology ran lot quicker. Here are some statistics (from memory)
Take 1: more than 100,000 (max set) errors and hence failed after 15 hours.
Take 2: ~25,000 errors in 7 hours
Take 3: 3,000 errors in 1 hour
Take 4: <1,000 errors in 25 min.
The dataset was HV/MV network with ~18,000 km lines, ~30,000 transformers and ~300,000 poles.
HTH.