idea Make ArcGIS Pro Faster (Benchmarked by ArcMap) in ArcGIS Pro Ideas

Make ArcGIS Pro Faster (Benchmarked by ArcMap)

JeffBishop — Fri, 20 Aug 2021 19:07:56 GMT

Simple idea.

GeoNet is flooded with complaints of how slow ArcGIS Pro is.

64Bit Architecture was supposed to bring speed.

Simple operations such as opening, saving, selecting, etc are sloooow.

Geoprocessing takes forever and makes my PC sound like it's going to fly.

I have compared the performance between Pro on my workstation grade laptop to my crappy admin laptop using Map and Map wins out solidly on almost everything.

Pro has a nice UI and flow to it, but suffers from MAJOR performance issues on even the most powerful of machines.

Working with local datasets has also not seemed to help at all.

For reference, my workstation running pro has:

8 core (16 Threads) Xeon 2.4 GHZ

32 GB of RAM

NVIDIA Quadro RTX300

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

JamalNUMAN — Thu, 02 Apr 2020 18:35:36 GMT

This has been thoroughly discussed here:

ArcGIS Pro: 2.4.2: In general, ArcPro has less performance than ArcMap,

I found out myself that the performance in Pro 2.5 much better than 2.4

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

JeffBishop — Thu, 02 Apr 2020 19:13:59 GMT

Yes thank you, that post was very helpful and I have reviewed it.

I am currently using 2.5 and in fact it is the only version i have used.

I would have really been frustrated with prior versions if they were slower than the already slow V 2.5!

I am still using Pro, but running all of my geoprocessing in ArcMap as well as other operations that are faster there.

This is a very annoying workaround, but necessary to keep up my productivity.

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

KoryKramer — Mon, 06 Apr 2020 17:48:16 GMT

Hi Jeff Bishop‌. Sorry to hear that you're seeing performance issues when comparing geoprocessing between ArcGIS Pro and ArcMap. In order for this to be actionable, the geoprocessing team will need additional details.

Can you share more information about what tool(s) you're running and share the execution time taken for the tool(s) to complete in ArcMap vs. doing the exact same thing (same dataset, same parameters, etc.) in Pro?

If you run in a blank project, with no maps, using the same dataset, is the execution time still slower in ArcGIS Pro than in ArcMap?

In ArcMap, do you run tools with Background Geoprocessing? It would be helpful if you're able to share a project package from the Pro project used to document the times above - it would be good to see how many maps and other items are in the project. Send to kkramer@esri.com and if needed because of size I can set up a secure ftp.

Thank you!

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

MollyMoore — Mon, 13 Apr 2020 18:00:50 GMT

I am also running into major speed issues in ArcGIS Pro 2.5 when trying to accomplish very simple tasks that makes Pro practically unusable for my workflows. Right now, my biggest issue has been with definition queries.

When I set a definition query on a feature service layer with around ~11,000 features, it takes anywhere from 3-8 minutes for the Pro project to become responsive again.

When I set a definition query on the same dataset with the same computer and connections, it updates instantaneously.

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

JeffBishop — Mon, 04 May 2020 19:12:00 GMT

Kory. Sorry for the late reply.

So due to the nature of my work I can't share anything.

With that being said, I have determined if I keep my projects simple, they perform better.

The issue is, I would like to have multiple maps, layouts, etc in a project, but Pro will bog down if I do so.

At this point, it is one map with maybe 2 layouts max.

The other issue is Scenes. Man they bog down and make my PC sounds like its going to fly!

I would love to do my 3D viz work in Pro, but it is too choppy. I use Google Earth Pro still at this point.

I would use ArcGIS Earth, but it has its own issues and lack of features compared to GE Pro. But that is another topic altogether!

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

KoryKramer — Fri, 08 May 2020 12:44:45 GMT

Hi Jeff. Given the detail about the issue being worse when working in larger projects, without specifics about exactly which geoprocessing operations, it sounds like the work that the ArcGIS Pro geoprocessing team has done in 2.6 may alleviate much of what you're seeing.

The team has taken some operations that open from ribbon buttons and context commands, like Select By Attributes, Add Join, and Calculate Field, and built them into simplified windows that run in an immediate mode which reduces the overhead of working in large and complex projects. These tools can run even when longer-running processing tools are running in the background geoprocessing thread (using the Geoprocessing pane), which will also make you more productive. If you would be willing to be part of the Pro 2.6 early adopter community, we will have availability of a beta release of the software within about a month so you could test some workflows that you aren’t able to share and let us know if you see any improvement.

If you're interested in testing your workflows with larger projects in Pro 2.6 beta, please let me know at kkramer@esri.com.

Thank you.

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

MarcelSt-Germain — Mon, 05 Oct 2020 18:55:55 GMT

Yes, Still Very Slow in 2.6.2

Maps, for me anyway draw faster than ArcMap. Unfortunately, working in the layout is far, far, far slower than ArcMap.

It's nice to have the elements in TOC, being able to lock them, name them. But, selecting and element take minutes not second. I try to uncheck the map to speed the work in layout but, see no changes. Each operation takes forever.

Do not know if it's because of import from ArcMap projects.

Also, very frustrating to make change and thinking it's finished and see changes haven't been accepted. By example, in scale line, I change map units, write the label test I want, select the division value, divisions and subdivisions to see that label haven't changed or division value or... always to make changes again and again until it's finally working. Finally, find that I have to wait minutes between each entry. So can take 5 to 10 minutes were in ArcMap it takes less than 20 seconds.

64 bits was a good news years ago to speed up ArcMap but, the result is very poor in the implementation for Pro.

Maybe, after importing things, need some optimization. Can't find a wait to make it.

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

JeromeHaaland — Tue, 06 Oct 2020 21:39:26 GMT

Wish I could upvote this 10 times.

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

SimonWatkinson — Tue, 06 Oct 2020 23:58:11 GMT

... yeah... wow... what's going on, guys? why should it take 20 seconds to get the symbology pane up? why should it take 40 seconds to change the text of a layout label? what is going on with your software. I have a pretty decent machine, I think: 32 GB RAM, INTEL XEON SILVER 4108 CPU @ 1.8GHz x 2 NVIDIA Quadro p2000.

What's going on with the code execution with these long wait times? Why should the number of layers or the location of the data mean anything for simple operations like this?

The productivity hit on my team caused by using ArcGIS Pro is in the order of 20%. People lose concentration because they get bored waiting for a response.

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

Aaron — Thu, 12 Nov 2020 19:39:46 GMT

No change in 2.6.3. I just don't understand the need to hit the network (or local storage) storage so often. At least be able to disable the catalog view from scanning the whole directory recursively.

No way it's my specs... i9@3.6GHz, 64GB RAM, 1TB M2 SSD, GeForce RTX 2080 Ti.

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

JeanetteHarlow1 — Sun, 15 Nov 2020 16:00:59 GMT

Please fix this.

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

MichaelNau1 — Wed, 13 Jan 2021 15:23:01 GMT

I can deal with some long processing times but layouts should be the easy part. I can not finish a map these days. Hours of waiting to edit text, graphics, scale bars, legends and locations of a few imported images. This is getting out of control.

Please if anyone figures something out and let us all know so I don't lose my mind.

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

ZachPorteous — Wed, 13 Jan 2021 19:45:06 GMT

I second all of these sentiments. Working with even simple graphics and text in Pro layouts becomes a huge laborious task. People ask me for edits that are necessary at a timely basis but Im just over here waiting for Pro to respond. All data held locally. 32 GB of RAM. No other resource intensive applications open on my computer. What's going on under there? Why is it necessary to own a super computer, or invest in cloud GPUs to run your application well? I'll experience the same amount of lag in Illustrator, only after adding hundreds of layers with the same comp specs.

- Also, I have Pro on the Absolute lowest graphics settings, important to add.

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

LaurenWinkler — Thu, 14 Jan 2021 01:18:47 GMT

Opening geoprocessing tools is noticeably slower in ArcGIS Pro

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

DarrylAlbert — Tue, 19 Jan 2021 19:29:02 GMT

Quite frankly this software is a joke. It's all great until you go to use it. What is happening in my situation is everything is working just fine, then boom, the hammer drops and Pro says I'm not working on this project any longer. Things that worked fine 3 minutes ago are taking minutes to update. Simple things, like clicking on a locally stored annotation feature class. Might have been instantaneous 3 minutes ago, now for the rest of the afternoon each click takes 30-60 seconds to resolve. The behavior is random and we can't seem to pinpoint it to any data sets, times of day, network issues, or other computer behaviors.

Our whole company seems to be having this issue, it's not just me. We've tried everything outside of hiring a rocket scientist look into it. The worst part of this is the ESRI techs answering some of these questions act like this is the first they're hearing of this. It's a joke, the software is a joke, and it's not looking good for ESRI.

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

TamirNof — Tue, 02 Feb 2021 23:12:42 GMT

I told my friends how lovely is ArcGIS Pro. But, when projects are getting bigger, it starts malfunctioning in basic functionality, like Simple labeling, IDENTIFY works like a nightmare, pan and zoom. etc. My project has about 10,000 point features with simple symbology, about 5000 polylines that only 100 of which are turned on, and 1000 polygons, which are only 5.

I am really frustrated and disappointed, especially after recommending my friends to move to pro (ArcGIS pro 2.7.1).

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

JeanetteHarlow1 — Fri, 19 Feb 2021 11:30:28 GMT

No change in 2.7.0.

Wondering if ESRI is spreading itself thin with expanding into new technologies rather than actually improving the "new and improved" workhorses.

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

KoryKramer — Fri, 19 Feb 2021 14:17:40 GMT

Hi @JeanetteHarlow1 Sorry to hear that you're experiencing performance issues. I double-checked the comments on this thread and didn't see any details about the nature of the performance problem you're seeing, so while the Pro development team is always working to improve performance, with the upcoming Pro 2.8 release being very tightly focused on performance and quality improvements, it would be impossible to say whether the work will help with what you're experiencing specifically.

It looks like we have had staff try to contact you to work on this together, but have not received any response. Maybe they had an incorrect email. We'd like the opportunity to look at performance problems you're facing in ArcGIS Pro so that they might become actionable development issues to fix.

I'd recommend working through to start, which might help narrow down the cause of the issue. If it does not, and you continue to experience performance issues, the next best step is to work with Technical Support. Technical Support is the most effective way to convey the information needed for development teams to act on the issue. It provides a trackable object (this may be a Case number and a bug number, if applicable) that can be referenced in the future.

I want to emphasize that we understand there are opportunities to improve ArcGIS Pro performance, and there are some great improvements on the way. But because performance can be affected by so many factors and specific circumstances, we can't be sure that the improvements coming in ArcGIS Pro 2.8 will address what you're seeing. Please let us know if you're able to provide more information about performance issues you're seeing in Pro.

Thank you!

Re: Make ArcGIS Pro Faster (Benchmarked by ArcMap)

MichaelNau1 — Fri, 19 Feb 2021 17:14:50 GMT

Im happy to give you any info or details about the issue. It would seem that regardless of system or data being used this is an issue across the board. Hopefully the next update helps but if there ia anything i can provide please feel free to ask.