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:
Application: ArcGISPro.exe
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 ArcGIS.Desktop.Mapping.MappingModule+<>c__DisplayClass443_0.<CreateNewMapAsync>b__0()
at System.Threading.Tasks.Task`1[[System.Int32, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InnerInvoke()
at System.Threading.Tasks.Task.Execute()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at ArcGIS.Desktop.Mapping.MappingModule+<InternalCreateNewMapAsync>d__1191.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at ArcGIS.Desktop.Mapping.MappingModule+<InternalOpenCreateNewMapAsync>d__1334.MoveNext()
Exception Info: System.AggregateException
at System.Threading.Tasks.TaskExceptionHolder.Finalize()
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.