Poor performance on a packaged project

[mikkokangasmaa]

I'm trying to share a project package through an ArcGIS enterprise portal. When the package is downloaded from the portal and opened locally it has very poor performance. Simple geoprocessing steps like clip can take up to five minutes to complete. 

The project includes raster data and it's 18gb in size. Is it too large to be shared like this or is there something that could be done to improve the performance? 

[DanPatterson]

It is shared outside your organization?

Did you retain geoprocessing history? Did anything in the link below prompt warnings if you went through the share tab?

Share a project package—ArcGIS Pro | Documentation

or were you using the Project Package tool, which allows for other options?

Package Project (Data Management)—ArcGIS Pro | Documentation

[ShaneONeill_144]

There are a number of factors that can contribute to ArcGIS Project size, and therefore, can affect performance

1. Maps
   • In the Catalog pane > Maps > the maps added to the project will show up here. If they do not need to be in the project or are no longer needed, consider removing them to cut down the size of Project.
   •  http://pro.arcgis.com/en/pro-app/help/mapping/map-authoring/maps.htm
2. Geoprocessing History
   • The geoprocessing tools that are run are logged and saved with the project. Detailed information about each GP tool ran can be re-opened. This will grow the GP History tool, as time goes on. Clearing this if not needed will also help bring down the size of the project.
   • http://pro.arcgis.com/en/pro-app/help/analysis/geoprocessing/basics/geoprocessing-history.htm 
3. Data/layers in the maps
   • Depending on what type of data is being added to the maps, these can take up space in the project. If data is not needed, then consider removing them as needed.

Consider also taking a look at the following and implementing the suggestions outlined before packaging the project.

• Troubleshooting Performance Issues in ArcGIS Pro