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?
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
Solved! Go to Solution.
...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&sea...
At least that can help you rule out a few things.
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?
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 🙂
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.
Hmmm...strange. Here are a couple things to try first:
Any additional information you may have to help me troubleshoot this would be great.
Hi,
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.
B
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
...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&sea...
At least that can help you rule out a few things.
Thanks. I'll try this right away...