{"id":73041,"date":"2016-07-26T13:56:44","date_gmt":"2016-07-26T13:56:44","guid":{"rendered":"http:\/\/www.esri.com\/arcgis-blog\/products\/product\/uncategorized\/troubleshooting-performance-issues-in-arcgis-pro\/"},"modified":"2023-11-02T16:11:47","modified_gmt":"2023-11-02T23:11:47","slug":"troubleshooting-performance-issues-in-arcgis-pro","status":"publish","type":"blog","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/3d-gis\/3d-gis\/troubleshooting-performance-issues-in-arcgis-pro","title":{"rendered":"Troubleshooting Performance Issues in ArcGIS Pro"},"author":6421,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"_acf_changed":false,"_searchwp_excluded":""},"categories":[23771],"tags":[772342,772332,31631,30321],"industry":[],"product":[36561],"class_list":["post-73041","blog","type-blog","status-publish","format-standard","hentry","category-3d-gis","tag-cpu","tag-framerate","tag-gpu","tag-performance","product-arcgis-pro"],"acf":{"short_description":"How to use built-in diagnostic tools and settings to troubleshoot common performance issues in ArcGIS Pro","flexible_content":[{"acf_fc_layout":"content","content":"

ArcGIS Pro is a 64-bit, multi-threaded application that takes advantage of modern computing architecture.\u00a0 That architecture is a big advantage for ArcGIS Pro, but it does make it a little harder to troubleshoot performance issues when they do occur.\u00a0 This article will discuss those issues and tools you can use to troubleshoot them.<\/p>\n

Since ArcGIS Pro uses your GPU to accelerate rendering, the first thing a user with ArcGIS Pro should do is update their GPU driver directly from the manufacturer (e.g. NVidia, AMD or Intel).\u00a0 New driver releases not only fix bugs and increase stability, but also can give performance increases as well!\u00a0 Note that “manufacturer” means the GPU vendor in the case of a desktop computer, but if you’re using a notebook computer, then you’ll need to get your driver updates from the manufacturer of the notebook itself.<\/p><\/blockquote>\n

The performance problems you may experience in ArcGIS Pro have four main categories:<\/p>\n

    \n
  1. \n

    LOW\/INCONSISTENT FRAMERATES: When you observe that the display feels \u201cjerky\u201d or unresponsive to navigation commands, it\u2019s possible that you\u2019re experiencing low or inconsistent framerates.\u00a0 Usually this is related to the volume of data that\u2019s being loaded or displayed for a given view.<\/h4>\n<\/li>\n
  2. \n

    APPLICATION UI IS GREYED OUT: When the commands on the ribbon, context menus, or in your panes are greyed out, this means some part of the application has executed code which must return before the application can receive other inputs.\u00a0 This greys out portions of the UI.<\/h4>\n<\/li>\n
  3. \n

    OPERATIONS ON LAYERS IN YOUR WEB GIS ARE SLOW: When you\u2019re working with Web GIS layers from on-premises\/hosted Portal or ArcGIS Online, the map may seem to take a long time to load, or context menu options may seem to be greyed out for a long time.\u00a0 Usually this is related to network issues (congested or saturated network resources), or it could indicate that the server itself is operating at a high load.<\/h4>\n<\/li>\n
  4. \n

    A LAYER SEEMS TO REDRAW FREQUENTLY:\u00a0 When some layers seem to disappear and redraw almost constantly, or after each navigation.\u00a0 Usually this is a problem with the layer\u2019s\u00a0caching options<\/a>\u00a0\u2013 which are available in the layer properties dialog\u2019s \u201cCache\u201d tab.\u00a0 Try changing this option to the \u201cKeep cache between sessions\u201d option to resolve the issue, unless the caching option is chosen for a specific reason (e.g. layer is updated regularly).<\/h4>\n<\/li>\n<\/ol>\n

    The developers of ArcGIS Pro have built in some tools to help you troubleshoot performance issues and give a little more info to solve the problem. \u00a0Below is more information about these tools, and some possible suggestions to try and work around the problems. \u00a0If you\u2019re still having trouble, or you think you\u2019ve found a bug, don\u2019t hesitate to report it to support@esri.com or by calling directly!<\/p>\n

    Diagnostic Tool: \u201cdrawing\u201d indicator<\/h2>\n

    When the graphics system is still loading data or properties to do the work of rendering, there is a \u201cswirling\u201d indicator displayed in the lower right corner of each view.\u00a0 When this is still moving, it means the graphics system is still accessing data needed to render the view.\u00a0 If it remains moving for a long time, it can indicate an excessive amount of loading is occurring, or that loading is taking a long time.\u00a0 This can indicate network congestion or scalability issues if you\u2019re working with Web GIS layers coming from your on\u2014premises, hosted or ArcGIS Online portal.<\/p>\n

    \n

    \"Drawing<\/a><\/p>\n

    The drawing indicator shows when loading and drawing is still happening.<\/p>\n<\/div>\n

    In more recent versions of ArcGIS Pro you’ll also see a pause button next to the drawing indicator.<\/p>\n

    Diagnostic tool: Performance readout\/overlay on the view<\/h2>\n

    The graphics system inside of ArcGIS Pro is constantly monitoring the framerate and other stats about the views you\u2019re displaying.\u00a0 You can get a readout of this information by pressing \u201cShift-E\u201d with the map view focused.\u00a0 This will display a line of statistics at the top of the view (see screenshot below for an example).<\/p>\n

    \n

    \"Diagnostic<\/a><\/p>\n

    Note: In ArcGIS Pro 3.2 and later, the Shift-E shortcut is disabled by default.<\/p>\n

    To enable it, go to the shortcuts menu by pressing F12.\u00a0 Expand the Global group and check the box next to “drawing performance overlay”:<\/p>\n

    \n

    <\/p>\n<\/div>\n

    The diagnostic readout shows information about the status of rendering as an overlay on top of the view.<\/p>\n<\/div>\n

    This readout is useful for detecting and troubleshooting LOW\/INCONSISTENT FRAMERATE issues.<\/p>\n

    Each segment of this readout gives you information about the rendering system.\u00a0 Below are descriptions of each segment (color coded for easier understanding) and possible troubleshooting actions you can take based on this readout.<\/p>\n

    EXAMPLE READOUT:<\/h2>\n

    DirectX11 High 40.461 (3.103) FPS 266813 Tri\/F 10.77M Tri\/Sec | MemMb VB 69.00 IB 0291 Tex 565.4 | TrMb VB 9.62 IB 0.004 T1.2 | Tile 99 E 511 C | Unlocked | 1854X954<\/p>\n

    DirectX11 = you\u2019re running in DirectX11 (DirectX 11) mode – in older versions this may say “DX11”.\u00a0 This section will say “OGL4” when you\u2019re in OpenGL mode.<\/p>\n

    ACTION:<\/strong> If you\u2019re having trouble with performance, you can try switching to OpenGL, also upgrade graphics card driver from MANUFACTURER site (not from windows update).\u00a0 Some GPUs may have better performance in OpenGL.\u00a0 In ArcGIS Pro 3.2 and later you can also switch from DirectX11 to DirectX12 if your hardware supports this.<\/p>\n

    NOTE:\u00a0<\/strong>If this readout says \u201cWARP\u201d then ArcGIS Pro was unable to detect a GPU that supports the required capabilities, and is using your CPU to emulate a GPU.\u00a0 This will in general result in poor performance.\u00a0 Try updating your GPU driver from the manufacturer\u2019s website (NOT from windows update) or switching from DirectX to OpenGL in\u00a0PROJECT->Options->Display.<\/a><\/p>\n

    High\u00a0= you\u2019re running in HIGH rendering detail<\/p>\n

    ACTION:<\/strong>\u00a0 If your framerate is low in 3D, try LOWERING rendering detail to one of the lower settings\u00a0in Display Options<\/a>.<\/p>\n

    40.461 (3.103) FPS\u00a0= this is the average (and minimum) FPS for a short period of time.<\/p>\n

    ACTION:<\/strong>\u00a0If Average is high but minimum is low, the user is experiencing \u201cstuttering\u201d.\u00a0 Usually this is a result of trying to load or render data that exceeds the GPU\/Memory\/CPU resources available.\u00a0 Try lowering the\u00a0\u201cout beyond\u201d parameter of distance visibility<\/a>\u00a0to something closer, so you\u2019re not trying to load so much.\u00a0 If overall FPS is low, it could indicate too much geometry in the scene for your graphics card (see the next item).\u00a0 Again, you can try lowering rendering detail or tightening distance visibility parameters.\u00a0 You can also try to generalize your geometries \u2013 see the \u201cExternal Tools and related links\u201d section below.<\/p>\n

    266813 Tri\/F=\u00a0 the number of triangles being displayed per frame.<\/p>\n

    ACTION:<\/strong>\u00a0If this goes too high, it will result in poor performance (FPS will be lowered beyond an acceptable amount).\u00a0 Try\u00a0lowering distance visibility<\/a>\u00a0for layers with lots of geometry, or lowering rendering detail setting.<\/p>\n

    10.77M Tri\/Sec\u00a0=\u00a0 the number of triangles being processed per second.<\/p>\n

    ACTION:\u00a0<\/strong>This is a multiple of the framerate times the triangles per frame. \u00a0If this goes too high, it will result in poor performance (FPS will be lowered beyond an acceptable amount).\u00a0 Try\u00a0lowering distance visibility<\/a>\u00a0for layers with lots of geometry, or lowering rendering detail setting.<\/p>\n

    | MemMb VB 69.00 IB 0291\u00a0= these tell you how many Vertex Buffers and Index Buffers are being used.<\/p>\n

    Tex 565.4\u00a0= you are using this amount (in Mb) of texture memory on the graphics card.<\/p>\n

    ACTION<\/strong>: if the sum of the above two numbers exceeds memory that is installed on the GPU (remember 1024Mb = 1GB) you will begin to seeing stuttering due to swapping of resources to disc\/main memory\/somewhere.\u00a0 Lowering Rendering Detail will help with this as it results in down-sampling of textures.\u00a0\u00a0Changing the visibility range<\/a>\u00a0for \u201cout beyond\u201d will help too, as you\u2019ll have less texture and geometry in the scene.<\/p>\n

    TrMb VB 9.62 IB 0.004 T1.2\u00a0= This is the amount of information being transferred into\/out of Vertex Buffers, Index Buffers, and Texture memory.<\/p>\n

    Tile 99 E 511 C\u00a0= you\u2019re using 99 Elevation tiles and 511 \u201ccolor\u201d tiles.\u00a0 This is the number of tiles being used to draw the surfaces (elevation + color source like a basemap) in your current view.<\/p>\n

    ACTION:\u00a0<\/strong>None needed.\u00a0 This is informational only.<\/p>\n

    \u00a0<\/strong>Unlocked | 1854X954\u00a0= you\u2019re displaying a map view at 1854X954 pixels.<\/p>\n

    ACTION:<\/strong>\u00a0None Needed.\u00a0 This is informational only.<\/p>\n

    These numbers are calculated for all views separately, so the numbers will be different per-view.\u00a0 \u00a0In a Layout view, you’ll see this readout for the layout itself as well as any map views inside that Layout.<\/p>\n

    \u00a0Diagnostic Tool: ArcMon (Diagnostic Monitor)<\/h1>\n

    ArcMon or Diagnostic Monitor is a diagnostic dialog contained in ArcGIS Pro.\u00a0 To access the ArcMon dialog, press CTRL-Alt-M.\u00a0 This will open the ArcMon readout as shown below:<\/p>\n

    \n

    \"Arcmon<\/a><\/p>\n

    The ArcMon or Diagnostic Monitor dialog gives diagnostic information about different parts of the ArcGIS Pro application.<\/p>\n<\/div>\n

    Note: the below section is for ArcMon in older versions.\u00a0 For more updated help on Diagnostic Monitor in 3.0 or later see\u00a0https:\/\/pro.arcgis.com\/en\/pro-app\/latest\/get-started\/arcgis-diagnostic-monitor.htm<\/a><\/p>\n

    The Diagnostic Monitor tool has four main areas of diagnostic readout.<\/p>\n

    Top Section: Performance Trend Graph<\/h2>\n

    \"Trends<\/a>When one of the line items below the graph are selected, this graph will show that line item graphed over a sampling period of time.\u00a0 By default it shows a graph of memory usage.\u00a0 One way to use this is to see trends in (for example) memory usage when a particular tool or workflow is executed in ArcGIS Pro.\u00a0\u00a0 As an example, in the graph above, you can see increases in memory usage (circled) when three separate global scenes are opened.<\/p>\n

    Middle Section: UI Task Log and GUI Hang Log:<\/h2>\n

    \"Task<\/a>This section logs a list of UI Tasks that resulted from your inputs, and times their execution, resume and wait times.\u00a0 Any cases where the UI was disabled for an extended period of time is logged in the GUI Hang Log section below.\u00a0 This can be useful for determining which executed task has resulted in an unexpected UI Hang as in the APPLICATION UI IS GREYED OUT issue listed above \u2013 this can then be reported to Esri support.<\/p>\n

    In the example above, a brief hang is logged for adding Map Notes to the existing map.\u00a0 Note: All times are listed in milliseconds.\u00a0 There\u2019s a whole library of research on the topic of response times and responsiveness testing, but as a general rule of thumb, delays of less than 400-500msec can be safely ignored, unless they are consecutive or regularly repeating.<\/p>\n

    \u00a0Bottom section: Activity Indicators for parts of the Application<\/h3>\n

    \"Activity<\/a>The bottom of the ArcMon dialog contains red indicator \u201clights\u201d to signify when a particular portion of the application is doing work.\u00a0 This is useful for getting some insight as to what portions of the application are exercised by your workflows, and also for troubleshooting \u201cAPPLICATION UI IS GREYED OUT\u201d and \u201cOPERATIONS ON LAYERS IN YOUR WEB GIS ARE SLOW\u201d issues.<\/p>\n

    These indicators, from left to right, indicate the following functions:<\/p>\n