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; } } }

Field Calc dead slow in 10.3; lightning fast in 10.2: what gives?

blueincspatial

When using the 'Field Calculator...' in the Attribute Table on selected records in 10.3, the calculations (even simple ones like setting an integer field = 1) are excruciatingly slow. When using the 'Field Calculator...' on selected records in 10.2, the calculations are blisteringly fast. See the attached image. The split screen shows the identical calculation performed on a selected set of simple lines. In 10.2, the calculation took 0.23 seconds. In 10.3, the exact same calculation on the exact same number of selected lines took 20.13 seconds. Why? 10.3 selected records field calc fail

I have been over all of the settings, environment variables, everything I can think of but there are no differences between the settings that I can see. Have I missed something? (Besides my marbles, I mean...)

TIA,

Brian

Find more posts tagged with

Accepted answers

RebeccaStrauch__GISP

...and if a different user doesn't have an issue on the same machine, try renaming the normal file and other tricks https://community.esri.com/docs/DOC-2121?sr=search&searchId=6d54ce19-8f1a-40da-aa7f-91908f399648&searchIndex=0‌

At least that can help you rule out a few things.

All comments

JakeSkinner

Hi BlueInc,

It could be a network issue. Try copying the data to the local machine and try the field calculator. What are the results?

blueincspatial

We work on the BC Government shared environment so the data is indeed networked, as are the various ArcMap versions. That said, I am/was able to copy and run the data from the C:\temp directory of the server with ArcMap10.3.1 running on it. The difference in the results were negligible: 19.39 seconds for the same calculation. Thanks for the response though 🙂

Robert_LeClair

Hmmm...strange. Here are a couple things to try first:

Compact the file geodatabase using the Compact GP tool.
Install the 64-bit background geoprocessing from MyEsri.
Upgrade geodatabase to 10.3 schema via a right-click in the Catalog window.
Build an attribute index on the fields to be calculated if appropriate.

Any additional information you may have to help me troubleshoot this would be great.

blueincspatial

Hi,

I ran the compact from ArcCatalog but there was little difference in the calc time 17.45 seconds (actually, I think this is one of the things I had tried previously...)
We're on a government network and none of us can install apps so installing the background geoprocessing from MyEsri is kindof out.
Upgrading the GDB is greyed out in Catalog because the GDB is already at the correct version.
Adding an index on the ID field had negligible effect 17.3 seconds)

blueincspatial

p.s. I will be conferring with colleagues in the morning as apparently some of them do not have any trouble with Field Calculator in 10.3 while at least one other person besides me does. I will see if I can get the successful Calculators to take a poke at this test data. More to come...

Thanks for the feedback.

shan_sarkar

Hi BlueInc,

Have you tried performing field calculation by logging with a different user profile from your machine? I am suggesting this since you have mentioned that your colleagues aren't facing this issue. It may be a machine specific or a profile specific issue.

Regards,

Shan

RebeccaStrauch__GISP

At least that can help you rule out a few things.

blueincspatial

Thanks; yes, essentially getting different colleagues to try the same test while logged into the network share is the same thing. I did that just now and found that:

the ones who don't normally experience a slow 10.3 field calc, didn't. Their test speeds were all comparable at about 0.19 seconds.
for those who DO normally experience a slow 10.3 field cal, the slow down happens when in an Edit session only (18 - 21 seconds). When performing a field calc outside an Edit session, the time for the same test averages .48 seconds.

blueincspatial

Thanks. I'll try this right away...

blueincspatial

Well, resetting the Normal.mxd has fixed the problem. Thank you so much all of you and Rebecca in particular for your insights.

I had a couple of custom Addin toolbars in the mxt that of course are gone now that I've reset. I will at least be able to troubleshoot the issue now going forward.

Thanks again,

Brian

Robert_LeClair

Are you using the Field Calculator command (via a right click) or the Calculate Field GP tool? I've read the GP tool is faster.

RebeccaStrauch__GISP

you should be able to get the addin's back...if not with the .addin button, but manually adding or maybe moving.

That is the problem with resetting the normal, you do lose you customization....but sometimes it is helpful to start fresh, but at a minimum it is always one of the first things to test when things go haywire (and you can always rename it back if that wasn't the issue...assuming you kept the old as a backup )

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.