I have met and exceeded the recommended spec to run pro, but it is so very slow to do just about everything. Any Ideas?
1. Please contact technical support so they can help you through this issue.
2. Can you elaborate on what is slow? Is the UI greying out? Is the map display jerky? More specifics will help to figure out where the problem may lie.
Once data is loaded from a local source, it becomes unbearable to zoom, pan, and even identify. I can't even begin to try any processioning, because the application freezes. The ribbon does grey out, and the data being displayed is very large in size and blurry.
Brig,
From your comments it sounds like you're in Scene view (Global or Local) in 3D. Is that correct?
quick diagnostic: with the map view focused, press shift-e to bring up a diagnostic readout overlaid on the map display. This will tell us some more about what's going on. Please post a screenshot of this here.
Some troubleshooting tips:
1. Update your graphics card driver _From the Manufacturer's website_ (not from Windows Update)
2. try switching to OpenGL (in Project->Options->Display tab)
3. Please run the diagnostic linked here and post your results: Can You Run It?
Regards,
Jeremy W.
No I was in the Map tab. I have completely removed the software and re-installed it. It now seems to be working correctly.
Hi Jeremy
I tried this just to see what happens and got the following:
Can you shed some light on what information is being reported here or direct me to some useful info that would explain it please?
Tx
Devlyn
Jeremy,
Does Pro support Proportional Symbology? Also is there a way to get the measure tool to display in inches?
Brig
I agree, Pro is incredibly slow on routine functions. Good example, I have a class with ~2,000 fields, in 10.3 I can set layer visibility in in 15 seconds. In Pro it takes nearly 15 minutes, 5 minutes to load all the fields into the grid and 10 minutes to cycle through each field after clicking save.
Secondly, there is no way to save the visibility setting so this painful process needs to be repeated over and over.
To be fair, some of the more intensive tasks, such as spatial join, are faster in Pro.
Hi Tom,
Tested with a table that has close to 2000 fields and Field Views loaded all the fields in the view in a minute. Would you please share the File GDB that contains the table you are having an issue with? Send it to our Support team through an incident.
In Fields View, you can save any edits made to the layer properties using the 'Save' button in the view ribbon. Is the button not enabled?
Thanks,
Annie
GDB is too large to send, however you already have the data. The class I was working with is the ESRI 2014 demographic data for block group centroids. I inserted the class into a new project, opened the field list, unchecked visibility on everything except the ID field.
I realize I can save my edits for this specific class. What I was referring to by not being able to save the field settings was as in creating a .fvl file.
Also paging through hundreds or thousands of variables is very tedious in the table view. What is needed in Pro is the equivalent of the field visibilities (BA). With this tool it is quick to filter for desired fields, add or remove from visibility group, and if desired save these settings to apply to another class or the same class in another mxd (project). It is distressing to see such good functionality being degraded to the table view method of field control.
Tom Goeke
Staff Technical Analyst
Corp. Prop. - GIS
Ext. 77415
P Please consider the environment before printing this e-mail.
I just wanted to add a little to this discussion because this thread kept popping up on my search for sanity. A little history, started Pro with 1.0 and am now up to 1.4. My typical pattern would be: I would say to myself "I should test out Pro again to see if it is working ok", so I will start a new project. The software would run fine, so I would add more and more to the project thus getting deeper in to debt with the software. After a couple of days it would start hanging up, start random crashes, and eventually become unusable. I would then issue a support request and run through the default procedures: Upgrade the Graphics Card, remove Space Patterns tool box, etc etc, and eventually Repair the software. After that it would seem to work enough to get my project complete and out the door. I then wouldn't touch Pro for weeks/months because of my trust issues with it. Then a new release would come out and I would treat Pro like an ex-girlfriend and say to myself "Ohh she is looking good. Maybe this time will be different, she's proably changed..." only too realize she is still temperamental and unhinged.
All this leads to today: I think two modifications I have made have helped. I have an NVIDIA graphics card, and I had to turn on the Antialiasing - Transparency option to "Multismaple" within the NVIDA Control Panel. The next change and this I feel might be the important one. As I was changing my display settings back to OpenGL (I've switched many times to try to resolve my issues btw), I noticed that the display cache was at 36 Gigs!!!!!! HOLY MOLEY. With that storage it was pushing my storage threshold on my hard drive to over 90% capacity which I think is what was making my machine go a little bonkers. When going through the ESRI procedures we would eventually repair the software, and that would clean the cache thus allowing me to operate the software to get my projects out the door. This all feeds into my narrative of I would start out in pro fine but eventually crapola. What I can ascertain is as I would build the project up, I was eating more and more of my storage with the cache getting so large until I would hit some threshold of available space and boom it would all stop working. I'm going to continue testing, and am hopeful I have found the culprit. Hope this helps someone.
Thanks for this note. I have experienced exactly the same thing and searched for sanity. I've gone through all the recommendations to speed things up and no matter what I do, Pro is still significantly slower than Desktop even when working with data that is local. And it crashes. I so wish that your suggestions to clear the display cache (which only had a couple hundred MB), and setting the multi sample for antialiasing suggestions had worked, but alas, on my machine there appears to be no difference. GP tools take anywhere from 30 seconds to a couple minutes longer to complete in Pro than Desktop. I just wanted to thank you though because I take solace in finding others out there who are experiencing similar frustrations. I want Pro to work, and I want / need to incorporate it into my teaching and research, but ..... I too have the "trust issues".
Just as a follow up, it's been about a month since I've kept tabs on my cache, other than random crashes (typical in ESRI software) the performance is substantially better. All that being said, there are many features unavailable in Pro that make it more difficult than Arcmap to use for quick analysis. For the life of me, I can't figure out why they didn't develop a field statistic option with a right mouse click as found in ArcMap. If you want to total your area field, for instance, you have to run the Summary Statistics geoprocessing. I didn't realize how much I depended on that small simple tool until it became unavailable.
As a side note you can run python to calc your area
x = [row[0] for row in arcpy.da.SearchCursor("layer", ["Shape@Area"])]
sum(x)
Tony,
Note that https://community.esri.com/ideas/11923 is in the product plan for Pro. We'll hopefully see that this year.
I have been experiencing slow drawing speed in ArcGIS pro 2. I have noticed this most when I have a layout, versus a scene. I had been originally working in 1.4, but just upgraded to 2.0, I cleared the cache, and switched to webGL. I have been working with this file, which is large, for a few years, and this slow behavior just started recently. I cannot figure out what changed.
Any ideas why it is slow?
Same issue here. Using ArcGIS Pro 2.0. Tried to open a geotiff fil (870 mb) but just got stuk. I'm running on a server (dual 12 cores Xeon, 128 GB ECC DDR4 RAM and Nvidia Quadro 4000). The same file opens in seconds in QGIS and ARCMAP. I have tried OpenGL and DirectX options, cleared cache, set options to low/fast but nothing seems to be working. ESRI should really work this out. ARCGIS PRO is bricked and useless at the moment.
Can you guys take a look at the troubleshooting procedures listed here? In particular if you could provide a screenshot with the framerate showing (shift-e with the view focused to see the framerates) that'd be a great first step before calling Support directly. If it says WARP you're using the CPU to emulate GPU, probably due to needing a driver update or reinstall for your graphics hardware.
https://blogs.esri.com/esri/arcgis/2016/07/26/pro_performance_troubleshooting/
I have just updated the Nvidia graphics driver. I noticed there's improvement but still slow. I did two things to further speed up my processing:
1. Build pyramid for raster data. This made opening huge raster files instant.
2. For large vector data, I applied query to display subset of data. This also speed up rendering.
It's ok now. I can live with Pro but still feel a little let down since I'm trying to make transition from QGIS to ArcGIS.
I've had some performance issues with clipping and also doing large select by location functions. The latter got so bad I had to go back to ArcGIS Desktop to complete the work. It took about 3 seconds to do it in Desktop.
Jason, what type of database are you working with (file gdb, enterprise (if so, what RDBMS, versions))? Where is the data stored - local drive, network share, etc.? I realize that these don't necessarily isolate the issue if it takes a long time in Pro and seconds in ArcMap. That makes it seem the issue is with Pro...
Can you give us some steps to reproduce? What does the Select by Location look like? How many features in the Input Feature Layer? What Relationship? How many Selecting Features? Search distance, etc.? If you could list out steps and provide zipped data, that would be great. I understand that you may not be able to provide data here, but this is a good candidate for a technical support case which will be a more productive way to troubleshoot what is happening and if needed, get the issue directly to the development team.
Thank you!
It was a point feature layer in a gdb. It was a simple select by location where the points were completely within a polygon. No search distance anything like that. Maybe 800-1000 features in each polygon. I'll be happy to send some data if you want to send me an email.
Thanks, Jason. I just messaged you an email address.
I have found that ArcPro is slow and freezes when I create a layout.
Hi Sarah,
When is ArcGIS Pro slow; i.e. what are you doing in Pro that is slow and what is the performance comparison between Pro and ArcMap?
Have you run Can You Run It? from the ArcGIS Pro system requirements page? ArcGIS Pro 2.0 system requirements—ArcGIS Pro | ArcGIS Desktop
If it is freezing up when creating a layout, I would recommend logging a case with technical support. There will be some standard questions they'll want to go through to help troubleshoot what is happening. There are also a couple of blogs (Part 1 and Part 2) called WWTSD (What Would Tech Support Do?) Part I | Support Services Blog Reading through these will give you an idea of the troubleshooting process. Working through some of this on your own may help you figure out what is happening, or at least get things pretty well narrowed down before opening a case.
I hope this helps. Please do reach out so that we can help get Pro running smoothly for you!
Hello Jeremy,
Attached is a frame rate screen capture. I have created this map with this dataset repeatedly in the past year.
One day I opened Pro and it just would not load anymore.
This is a large dataset.
Thanks
Hello Kory,
I am running 3 (2.5) D models of a large parcel dataset, So I have not modeled this in ArcMap. I can test in arcScene.
I have not run the run it tool I will see that, but I'm not sure what that will do, I ran ArcPro successfully for months.
I will look at the blogs, Thanks!
Map View + Attribute Table & Map refreshes constantly whilst editing. Seems like every mouse click triggers a map & attribute table refresh (3000ish polygon records)... very painful experience. The same layer in ArcGIS for Desktop behaves much better... very poor experience with Pro (2.0.1) so far
Ryan, I'll message you offline to see if we can connect and maybe get a copy of your project and data to take a look at the issue.
I had problem with Arcgis pro .First I got a blue screen during the work and shut my pc down . I solved this problem by update the BIOS. But my ArcGIS pro was still very slow and crushed again and again . This problem is solved too , by replacing the old graphic card with a new one
I'm running a Dell Precision M6800 with 16GB RAM, Intel Core 1704940MX CPU @ 3.10CHz 3.30 GHz with NVIDIA Quadro K5100M. My my tech's machine is running a newer more robust machine: 64 GB ram, Intel Xeon CPU E5 2637 v4 & 3.5 GHz (2 processors), NVidia Quadro M5000.
Both machines handle Pro fairly well, but I am not seeing the vast improvements I would expect from this new multi-threaded 64bit app. Also, there are random latency issues my tech and I experience. Not deal breakers but annoying. Sometimes changing a symbol could take 10 seconds for the processing bars to go away and then update. Turning a layer on could be instantaneous or could take a few seconds. This seems to vary by the day and by project. In addition, geoprocessing doesn't seem to be enhanced from ArcMap, some even feel they take longer to complete.
Do others have these type of issues?
In addition, I wanted to know if those who are having a good experience with Pro, can give us their computer specs and workflow environment?
I'm running a machine well in excess of the minimum, and I too am puzzled by how Pro seems to do many things much slower than Arc. For example, changing symbology where the data is coming from SDE makes Pro so slow as to be unusable. Each change to a symbology property recalls all of the data from the SDE. This is not the case in ArcMap, where any change to the exact same SDE-sourced symbology is instantly reflected.
I'm not sure if this thread is still being followed, but I'd just like to chime in with my experiences as well. I'm trying to work through one of ESRI's 3D visualization tutorials in Pro, but can't even pan the map with 3D trees enabled.
I have followed the steps recommended earlier in the thread with zero success. Below are my results from Can You Run It? and the in-Pro diagnostic tool.
My drivers are all up to date, and I was running Pro with no other programs open while recording those diag results.
Hi James,
I reviewed the info you sent in, and with a bit of searching it appears the GPU you are using was a low-cost part (<$50.00) when it was released circa 2010 or so. You will also note that AMD considers this "legacy" hardware - meaning it does not actively update the drivers: https://support.amd.com/en-us/download/desktop/legacy?product=legacy3&os=Windows%2010%20-%2064 (Anecdotally I have an old HP laptop at home with the mobile version of this GPU...)
So unfortunately, while it "ticks all the boxes" WRT the system requirements, there are inherent limitations to its 3d capability and capacity. That is why the "recommended" requirements mention 2GB VRAM.
You can see in the readout you sent the "Tex" shows 608MB. This means textures alone are consuming more resources than your GPU has. These resources when this occurs will start paging out to system memory, and this incurs a substantial performance hit.
SUM: Your current GPU has very limited resources and is a "legacy" product per the vendor.
RECOMMENDED RESOLUTION:
a GPU upgrade (if possible) will definitely give you much better performance in 3D workflows. I think you'll find that a GPU with 2GB dedicated VRAM can be had for a reasonable price, that would give you a much better experience.
FWIW we're updating the system requirements for Pro 2.2 (in Beta imminently) to better clarify the need for GPU resources. While the above GPU should not see any challenges in 2D workflows, it is not optimal for 3D workflows.
Please let me know if you have any questions regarding the above information or recommendations.
Hi Jeremy,
Thanks so much for your prompt response. At your recommendation, I'll look into trying to upgrade my hardware.
Again, much appreciated!
James
Will the 2.2 system requirements specify for what purpose one would need the "bling" GPU (3D) versus what the minimum requirements are for most of us that do not have any need for 3D (and stubbornly will continue mapping in 2D 'till we retire). I'm having a hard time convincing upper management that we need to start getting computers outside of the normal "email checker" that is the default desktop config, on which Arc Map runs fine.
The changes we made to 2.2 system requirements boil down the shader model/level to more concise terms, and add an emphasis on dedicated GPU memory versus "shared" memory such as the integrated GPUs in Intel core i series or AMD APUs.
As to your request: while some users may prefer to continue in only mapping in 2D, Pro is an integrated 2D/3D GIS.
Consider that the ArcGIS desktop requirements previous to Pro also included GPU requirements, for usage by ArcScene and ArcGlobe.
But, if you need an argument to give your IT staff for an upgrade...
Per your readout in your post above (from 2017) you have a Quadro 600 - that GPU is an entry-level "Fermi" generation GPU. That generation of GPUs is also in "legacy" support from NVidia after the latest driver release, meaning no more driver updates.
Also the Quadro 600 has some known issues WRT "ghosting" and artifacts in UI elements when drawing on the non-primary monitor in a multi-monitor setup, probably due to some vagaries of windows' desktop compositing in modern OS versions.
We've reported this through our normal channels to NVidia, but any fixes WOULD NOT be available for Q600, due to its aforementioned "Legacy" status.
So hopefully those two arguments should be sufficient to get you a new GPU at least?
One more Q for you: did you ever send in the performance issue you reported above (issues with updating symbology when using SDE database) to support? Kory Kramer might be interested if you're still seeing this issue.
I just sent an email to him on that topic;
The Quadro 600 and the machine it's in will be in the dumpster in a few weeks.....it's replacement will contain "NVIDIA® Quadro® P4000, 8GB, 4 DP (7X20T)" (single, I considered two of them but had a very hard budget limit).
There has been much discussion about replacing workstation with new ones that will be capable of running Pro for the next 4 years, the minimum we are required to retain a machine (no matter what, you're keeping that machine for at least 4 years, we don't care what the software requirements are), with the understanding that we will likely need to get 6 years out of them (e.g the age of my machine). Emphasis on "You better pick out the right specs, you're not getting a new one for 4 years, period". A significant factor influencing our dilemma is that a new version of Pro seems to be out every 6 months, and we really can't be in a position where a bug is fixed in the next version, but we're hardware limited from upgrading to it. That is NOT how ArcMap versions are/were released. So with that in mind:
I really pushed for the NVIDIA card on the workstations, but due to limits on what we're allowed to purchase and how, there was no option to get ANY NVIDIA card with the other hardware requirements (memory, cpu, hdd) and stay under the budget limit. If someone REALLY needs to do something in Pro that only works with a NVIDIA card, we'll have one (1) available. Our goal is to make sure no one's doing anything that requires NVIDIA, though. Those of you with Dell Premium accounts will know what I'm talking about....TAA compliance.....ugh......
A few folks are getting slightly upgraded versions of the above (e.g one laptop is getting an I9 6 core) due to some very specific non-GIS work they do (e.g Adobe), someone's getting dual 12-core XEON's (Sasquatch Monitoring coordinator, that animal is very elusive and needs powerful real-time tracking models).
However, that still leaves me with a large pool of users and shared lab workstations ( I run two shared workspaces with 4 workstations each, and one has 2 laptops also) that still have the standard email checkers, and likely will only get as replacement, the standard email checkers. Arcmap runs fine on their computers: Pro does not. For example, on the standard email checker (I5 with 8 GB RAM and SATA SSD), the simple task of downloading an offline-capable feature service locks the CPU to 90-100% for several minutes and renders the machine unusable 'till the data is downloaded. "Create Local Copy For Editing" in Arc Map, however, on the same PC, takes less than a minute or 2, and the user is free to do other things meantime. Bumping the RAM up to 16GB "sorta helps", but the 360$ cost of the RAM is a deal breaker.
So here we can see that my "Email Checker' passes "Can you run it easily":
In this test, using a "small" feature service (not a lot of data, the "big" feature services (over 500 features) are where the 90-100% CPU blast really have effect), disabling whatever running apps that I can without setting off some IT alarm, and a freshly-rebooted Windows 10 computer, I can easily max out the CPU. FYI, whenever a CPU hits 90%, there's some workstation monitoring doo-hickey that triggers some alarm, somewhere, that I'm not supposed to "know about". I think the idea is "they" don't want software on the network that throttles up CPU's to that level, uses too much electricity, kills our LEED certification, destroys the planet.....what I do know about "it" is that once CPU passes 90% for a certain about of time, "it" lowers the priority of the process....
Leadership is having a difficult time grasping the messaging here: Less employees are going to be able to complete their assigned duties in a timely manner because the new software performs poorly on their computers."Why do we have to get machines that satisfy 3D hardware requirements? We will never do 3D? Who made this a requirement? Did they ask us?". I'm just the messenger.
We can compare "Can you run it" results all day long and check a box "well it passes the test", but at the end of the day, I'm required to run Antivirus, Workspace monitoring and control, Office, etc...software that also competes for hardware resources. I'm pretty confident few, if any, ESRI customers run nothing but base OS and Pro and no other software installed in a corporate deployment scenario. In my email-checker-can't-download-map example, it passes the "Recommended" Can you run it results easily. For example, the standard email checker laptops ONLY get the shared/integrated GPU, from what you're saying, that doesn't meet the requirements (and could be an issue when we call TS).
In many other GN threads I've seen "Update the video driver" as a solution. We've very rarely had to update a video card driver to resolve an Arc Map problem. I can assure you, again, guessing that every corporate IT shop will share my opinion, having IT run around several times a year to upgrade video drivers (because ESRI is most certainly aware that most corporate IT policies prohibit GIS users from performing this admin-rights task) will be practice that ends abruptly after they realize how much extra work it generates.
An Idea for the "Ideas" site is brewing.....just shooting from the hip here, how hard would it be to "comment" out all the 3D code in Pro? This exemplifies my ignorance of how Visual Studio works, but I've developed a lot of stuff where some particular part was generating so much grief that I just disabled it and told the user "Sorry, here's a partially functioning widget". In our case, the function we lose is 3D Unicorns, which I'm fine with, and I bet a lot of other folks would be too. My unrealistic vision involved going to My ESRI and downloading the "Crippled" version of Pro to install.....
I was asked to re-post a message I had posted elsewhere here to help add to this discussion.
I generally like the direction PRO is headed in but is anyone else experiencing terrible performance - just doing normal tasks locally?
I'm attaching Two screenshots, one showing my system specs, and the other one showing my GPU specs. My original post also had a third screenshot of my task manager at the time I was working. Unfortunately that shot was lost when moving this message to this thread. The Task Manager image showed my CPU at about 65%, My RAM at about 50% and my GPU at roughly 80%. The screen shot of my task manager was taken while I have two instances of ArcGIS Pro running. In one instance I changed labeling properties for a layer. In the other instance I was zooming to a new extent. This initiated the spinning wheel indicating that PRO is working....
ArcGIS Pro has been in this state for over 5 minutes now with the task manager running this hard.
Granted - my maps ARE feature and graphics intensive, BUT I could perform this same operation with two instances of ArcMap on a slower machine in about 3-4 minutes. PRO should be faster than ArcMap, not slower.
Is anyone else experiencing this? I don't want to have to send all of my data to ESRI and work with technical support to find out simply that they replicate the problem... I sincerely want ArcGIS PRO to perform like the next generation GIS platform. As I mentioned above, I do like the general direction they are heading with respect to PRO but I am extremely frustrated with migration when not only was the transition somewhat less than intuitive, but now after migration of my workflows I'm finding myself LESS productive than I was on ESRI's old product on a less capable computer.
You're not going to like this, but you're going to have a miserable Pro experience with that budget processor and slow memory, regardless of # of cores and getting "Optimal' in "Can I run it". I'm having your same experience with the opposite-of-budget-hardware.
With regards to deciding to call tech support, PLEASE!. Exactly what we need is more than one or two people out of the hundreds (thousands) calling TS with performance problems. If they can repro your issue, it will get fixed. It has been my experience that the development team takes seriously reproducible issues.
It doesn't matter if your data is coming from a SDE on another planet and 4,232 network hops away, a local FGDB on a class 50 SSD, or a floppy drive on a TRS-80. Your expectation that it should perform as well as, if not better, than the same data source on Arc is not only reasonable, but IMHO a "business requirement": The software which your business depends on should not get slower with the next version.
Call TS!
Thomas:
In your ArcPro System Requirements Lab Analysis results it shows a green check next to most items except for CPU Speed and Video Crad where you have an i icon. Do you have any idea what the i icon means per these results?
These are "info" items - they're not tested.
The CPU is "info" because we only specify core count, not minimum Ghz.
(We may consider changing this as intel has multicore Xeons with lower clock rates.)
The Video Card is "info" because the sub-requirements below are the criteria for the test.
Lastly the "dedicated video ram" isn't a REQUIREMENT since you could have an integrated video card that uses system memory. However we RECOMMEND 2GB minimum dedicated VRAM as that will give you better performance than shared memory.
Reduce ArcGIS Pro network traffic
サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
