User Guide > Retrieving Data Source Metadata > Tips on Introspecting Large Data Sources > Understanding the Introspection Plan Implementation Phase
 
Understanding the Introspection Plan Implementation Phase
After you select the resources to include and specify any filters for newly found resources, TDV displays a list of the resources in the introspection plan.
The introspection plan is displayed. You can change it by clicking Back and changing the filters and other settings as described in Introspecting a Data Source.
After completing the list of resources to be introspected, click Finish and the introspection task is launched. The introspection task status is displayed, along with a summary of the actions taken.
If you close Studio before finishing, introspection continues to run in the background.
The following describes the introspection and performance considerations:
Introspection happens concurrently, one thread per container.
Batching is applied to further improve performance.
For each container, TDV evaluates the contents and breaks it into chunks of resources that have a common parent container and resource type. These chunks are broken into pieces smaller than the maximum introspection batch size. If this size is not defined for the data source, the chunks are divided into several pieces equal to the number of processors, or half the data source maximum connection pool size, whichever is less. This parallelism degree can be overridden within the data source capabilities file using introspect.override_parallelism_degree.
Note: This override is only available for introspection, not resource ID fetching.