Hi @KIRKQUINBAR, if you enable Predictive Optimization at the metastore level in Unity Catalog, it automatically applies to all Unity Catalog managed tables within that metastore, no matter which workspace is accessing them. PO runs centrally, so there’s no duplication of compute across different workspaces. However, compute usage is tied to table activity. If multiple workspaces are actively writing to the same tables, PO may kick in more frequently since it’s triggered by data changes. This could lead to an increase in overall compute usage and potentially higher costs.

To keep track of optimization activity and performance, you can use system tables like system.storage.predictive_optimization_operations_history. This helps you identify any unexpected behavior or spikes in compute usage related to predictive optimization runs.