Consideration for ETL Performance

Previous TopicNext TopicContents

The ETL process for P6 Reporting Database was designed for multi-core processor systems. Instead of using a serialized process, Java is used to create a multi-threaded process to run concurrent threads of SQL*Plus, SQL*Loader. This can result in multiple run threads on the various servers. This also means that the process can be adversely affected by having to compete with other applications sharing the same resources. Therefore, an ideal configuration would have dedicated cores available for each component in the process and a dedicated database instance with sufficient SGA allocation and high through put IO system.

This is an ideal configuration that is meant to minimize contention. By dedicating resources to each of the physical components, concurrent performance will be maximized during peak usage. Different steps in the ETL process put a variety of load on each component. In this release, there is no concurrent processing occurring simultaneously on both ODS and Star servers. Therefore, from the ETL perspective, ODS and Star could share the same physical hardware. You should consider concurrent reporting usage when determining the correct CPU requirements for ODS and Star.

Related Topics

Network

Memory

Extract and Load



Legal Notices
Copyright © 1999, 2014, Oracle and/or its affiliates. All rights reserved.

Last Published Friday, January 31, 2014