You can configure Dgidx for enhanced performance.
Although this guide deals with MDEX Engine performance, since the Dgidx program is involved in the indexing process, it is important to plan for adequate Dgidx performance as well. It is especially important to plan for Dgidx performance if you have a large data set.
Oracle recommends provisioning your hardware for running Dgidx using these estimates:
If a record takes longer than 60 seconds to process by Dgidx, Dgidx prints out a warning enabling you to identify and fix the record. This information can be useful to you if you need to identify a record with extremely large numbers of property assignments. This may occur as a result of an issue with the ETL process. After you identify the record, you can review it to decide whether all of its assignments are required by the application.
