Why is ArcGIS Pro so slow? To select assets, field calculate, display layers, change symbology... the easiest of tasks that are commonly utilized within ArcMap are a drag on the software.
When will ArcGIS Pro become faster than ArcMap? That will be the day it could replace it as the goto product for GIS professionals.
I think there is an issue with Pro and multi-threading - as my assumption is that a 64 bit application (that claims to be able to take advantage of multi-threading) should run faster on my machine than a 32-bit ArcMap application. Like the OP, I am also seeing much slower performance with Pro vs ArcMap on my machine. Doing very simple things like calculate field, selecting features within an attribute table, doing edits, changing symbology all take substantially longer in Pro...
As a side note, I am getting crashes when I try to Insert a new map into the project that appears to be in relation to Multi-Threading (but maybe I am wrong on that diagnosis).
Event Viewer shows the following:
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException
at ArcGIS.Desktop.Internal.DesktopService._IMapAuthoringService.CreateNewMap(Int32, System.String, ArcGIS.Core.CIM.MapViewingMode, ArcGIS.Core.CIM.MapType, ArcGIS.Desktop.Mapping.Basemap, Boolean)
at System.Threading.Tasks.Task`1[[System.Int32, mscorlib, Version=126.96.36.199, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InnerInvoke()
Exception Info: System.AggregateException
My machine specs are as follows:
All my data is local on a very fast 250GB Samsung NVME SSD (so read/write is not the issue here I am afraid). I am also running a NVIDIA Quadro M4000 GPU and ArcGIS Pro 2.0.1, but this issue first started occuring in 2.0.0 - I have submitted countless crash reports.
Our organization has a maintenance subscription so if anyone from support can reach out on this issue, it would be greatly appreciated.
Agreed, it's really the common tasks that were consistently instantaneous for years in ArcMap that all of the sudden are slow in Pro. This is really a spit in the face to end-users.
I think Pro communicates with the network more. It would be interesting to compare performance with working on versus offline which is possible in some configurations.
"I think Pro communicates with the network more." is an understatement. Think I found out why every single change to a symbology property takes forever and locks up Pro: Simply changing a symbol from "ArcGIS 2D: Circle 1" to "ArcGIS 2D Circle 3" resulted in 10,475 separate TCP calls evenly split between send, receive, and copy events which took 00:00:02.10 seconds to execute; the same exact operation in ArcMap? 0 TCP calls, 00:00:00.23 seconds to execute. Sometimes the delay is several minutes. It appears that with every symbology change, Pro is re-downloading the entire layer from the source. Why? Arcmap doesn't do this (and isn't as slow at common operations such as symbol styling). Making pure SQL queries to the same data in a variety of clients other than Pro is near-instantaneous. This is regardless of the layer cache settings applied in Pro (I tried all of them, same barely-usable response).
It would definitely be nice to see a real response of ESRI to your detective work regarding the TCP calls or ArcGIS Pro. Whether you are on to something, I can't say, but it does raise questions and points ESRI should look into.
Just imagine what happens when your network admin put real time virus scanning on your network and local machine and every one of those calls is intercepted by the virus scan before it goes through... The software is rendered useless. My experience mirrors yours in that Pro does generate even more network traffic than ArcMap. Anything that interferes with this affects the user experience and it can definitely be network side monitoring and port limiting.
I have also had this issue with virus scanning. ArcMap runs just fine using data saved in exactly the same location and using the same computer (above recommended specs). This is making it impossible to migrate to ArcGIS Pro as I can't even change layer symbology without the application freezing!