nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Network Topology Performance

TSmith

Hey all,

Had a question about the network topology operations performance. I have been working with a quite large sewer UN, and am wondering if this is the cause of disabling/enabling network topology taking so long. This UN has been in a file geodatabase that was zipped up and sent to us. Wondering if that is part of the performance problem.

There aren't any topology errors, but yet disabling it/re-enabling it takes a very long time (sometimes close to an hour)

Initial creation of the system tier took over 5 hours- is this normal behavior for a very large dataset? I am considering putting this into an enterprise geodatabase to see if that fixes the issues, or if this is potentially related to the bug involving growth of the EID tables. I also rebuilt/re-calculated all spatial indices. If anyone else has encountered this issue- what were your steps to resolve?

For context- I am using an earlier UN that was upgraded to UN 7, and my version of ArcGIS Pro is 3.5.4

Find more posts tagged with

Accepted answers

GIS_kiwi4

One thing I have personally noticed is the performance is leaps and bounds better when using a mobile geodatabase rather than a fileGDB. If you are working on a local machine then I would certainly encourage the use of a mobilegdb.

I agree with Robert's suggestions - having it local rather than on a shared drive is key.

Are you running it on a laptop or workstation.
Having a mid to high tier laptop definitely helps.

All comments

rkrisher

If you're seeing slowness in a mobile geodatabase, you can use the Logs tab in ArcGIS Pro Diagnostic Monitor to see what queries are happening and how long they're taking. Simply modifying the vertices of a line shouldn't take that long but there may be additional things like attribute rules that could be contributing to the additional time. Or maybe its an extremely long line with many features connected to it? If the slowness was on validate (and not edit) than there are other things you could consider, but it sounds like that's not the case.

JohnGoat

@gis_KIWI4 @RobertKrisher

Yes, I’ve noticed the same.

Especially operations like enabling/disabling topology or running Update Subnetwork are significantly faster in a mobile geodatabase compared to a file geodatabase. The difference is very noticeable.

That’s actually why I prefer using mobile.gdb in many cases.

However, despite that overall performance improvement, I’m still seeing occasional slowdowns during certain edit operations — particularly when modifying line geometries by reshaping vertices. In some cases, a simple vertex-based modification can take up to 40 seconds.

So overall processing tasks are clearly faster in mobile.gdb, but some geometry edits still feel unexpectedly slow. Have you observed anything similar on your side?

TSmith

Had much more success on an enterprise GDB- I will try on mobile GDBs in the future!

GIS_kiwi4

TSmith

The system tier has 45.1 million feet of pipe in shape_length, so around ~9000 miles of pipe. Definitely larger than most systems, I'm going to try this on a server environment and see if I run into the same issues.

rkrisher

Can you quantify "large network"? How many network features, or how many customers do you serve (it's approximate, since you don't have something like a meter layer you can query).

If you're experiencing slowness with a file/mobile geodatabase, make sure you are using it on a local disk instead of on a network share. Latency has a huge effect on performance when you're working in a client/server mode. In the same line of thinking, putting the database on an SSD instead of a HDD makes a big difference as well.

Other factors to consider are whether your machine has enough memory to build the topology in memory, or whether it has to use disk. If it is having to write to disk during enable, you will want to make sure you have enough free disk space and that it's a SSD.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.