Documentation about new workspace caching functionality in Pro 3.3.0

[Bud]

What's new in ArcGIS Pro 3.3 - Analysis and geoprocessing says:

The geoprocessing framework uses workspace caching to improve performance when running scripts or repeated processes. This improvement applies particularly to remote data sources, such as enterprise geodatabases.

Could details about that new functionality be added to the Pro documentation?

• What "repeated processes" does this new functionality apply to?
• Does it apply to Route Event Layers?
• How does it work? 
  • Caching comes with tradeoffs and raises lots of questions. We need to understand what impact it will have on real-world customers.
• Need more information.

Related:

1. New workspace caching in Pro 3.3 — Improved GP performance in EGDBs? (originally posted May 13th; moved from the Enterprise Geodatabase questions community to the Pro questions community)
2. Esri Support Case 03632162: New workspace caching in Pro 3.3 — Improved GP performance in EGDBs? (May 21st, 2024)
3. "New workspace caching...Would someone from Esri be able to help with that question?"
4. Layer Caching — How does Pro know when data was last updated?
5. Control caching settings for better performance in route event layers & query layers
6. Precomputed real-time linear referencing feature class (equivalent to route event layer)
7. Sample Script — Precomputed real-time linear referencing FC (equivalent to route event layer)
8. Length-based event layer: Linear referencing event layer that plots events along lines using the cum...
9. Optimize Route Event Layers
10. Route event layers - low performance

[DuncanHornby]

@Bud , sometime when a help page falls short on what it is explaining I have contacted ESRI, I assume their documentation team, through the link which I believe is at the bottom of every help page.

Just letting you and anyone else who reads this idea know that there is this method to contact ESRI on a specific page.

[Bud]

Thanks @DuncanHornby. I submitted feedback just now, as you suggested.

[Bud]

Esri Case #03632162 - New workspace caching in Pro 3.3 — Improved GP performance in EGDBs?

Please see the answer from the Product Engineers below. They are referring to the caching mentioned in the What's New article.

“That caching optimizes turning a catalog path (eg: "c:\myproject\x.sde\myuser.mytable"), which is the way you enter a dataset in GP, into an ArcObjects (AO) table object.

More specifically, we keep a list of catalog paths, and associated AO "NameObjects", these name objects are very light (keeps the workspace object & table name). Upon getting the same catalog path, we can quickly get the NameObject and from there create a fresh AO Table object.

This "creation of an AO Table object" can happen multiple times within a single GP tool operation… and of course multiple times across a python/pro session (which could use the same dataset in multiple GP tool operations).

Why it's particularly advantageous with egdb, is that creating the workspace (connection to the database) is a remote service call which can be comparatively slow.

This cache shouldn't cause stale table schema or stale table records.”