Best Practice for performing large calculations via UN Branch Feature Service - Error Time Out

P_Lalancette

Enterprise 11.3, ArcGIS Pro 3.3

Issue : Long term/large dataset editing time out via UN branch feature service connection (Utility Network Utility)
• Occurs on transactions of 100k+ via use of the Calculate Field GP tool. This time out appears to occur either due to processing time or feature count.

Aside from adjusting the pooling options in ArcGIS Service Manager (shown below), what other best practices can I follow when performing large calculations through a service? Is it possible to execute calculations using GP tools, such as Calculate Field, directly on the database connection?

gis_KIWI4

@P_Lalancette - Editing via the service is best practice. The highlighted setting is good enough I believe.
Your bottleneck possibly could be the number of instances you have running.
You only have 2 max instances.

If you have users using the same service at the same time then you will run into resource contention.

I would suggest raising the max to the number of vCPUs (or slightly more ) on your server.
Failing that try running the operation when there are no other users accessing this service.

Calculate fields on 100K records is not a "huge" update and there could be some other issues which might stop this. If this fails again, set the logging level to verbose and replicate the issue. There may be some additional information in the logs.

P_Lalancette

Thank you @gis_KIWI4 for the helpful suggestions! I will certainly look into these options as a possible solution.

RobertKrisher

If you have any attribute rules configured on a layer you are running a field calculate on, and you haven't already configured triggering fields to prevent them from firing, that could also be responsible for the slowness you're seeing.

P_Lalancette

@RobertKrisherGreat point about the attribute rules running at the same time as the field calculation. I appreciate you bringing that up and giving me the idea to check.