| Oracle® Retail Bulk Data Integration Cloud Service Implementation Guide Release 19.1.000 F31810-01 |
|
 Previous |
 Next |
| Oracle® Retail Bulk Data Integration Cloud Service Implementation Guide Release 19.1.000 F31810-01 |
|
Previous |
Next |
The performance of each of these components is influential in the overall performance of the system:
The application server(s) topology and configuration.
The BDI deployment approach.
The hardware sizing and configuration of the BDI hosts.
The hardware sizing and configuration of the applications that are connected to the BDI.
There are other factors that determine the performance of the overall system.
Number of partitions and threads used by the batch jobs.
Item-count and fetchSize used in the downloader-transporter batch job.
Item-count used in the uploader batch job.
Size of the data set
Performance of the Downloader-Transporter job can be tuned using the following options.
Partition
Thread
Item-count
fetchSize
Default values for "Partition" and "Thread" are 10. The Downloader-Transporter job splits the data set rows among 10 partitions. If there are lot of rows in a data set, increasing partitions and threads allow more parallel processing of the data, and can improve the performance.
Keep the partition and thread values the same so that a thread is assigned to each partition by Batch runtime. If there are more partitions than threads, Batch runtime won't start a partition until a thread is available to run.
Partition and Thread values for the Downloader-Transporter job can be changed from the "Manage Configurations" tab of the Job Admin GUI. Partition and Thread values can be changed just for an interface module.
The Default value for "item-count" and "fetchSize" is 1000. Item-count is an attribute of "chunk" element and "fetchSize" is a property in the Downloader-Transporter job xml.
The Downloader-Transporter job reads 1000 records from the database and sends data to Receiver Service for the destination. If performance of a Downloader-Transporter job is not meeting expectations even after changing partitions and threads, increasing the "item-count" and "fetchSize" values may improve the performance as it reduces the number of round trips to the database.
Memory utilization will increase as you increase the "item-count" value.
Performance of an Uploader job can be tuned using the following options.
Partition
Thread
Item-count
Default values for "Partition" and "Thread" are 10. The Uploader job splits the list of files among 10 partitions.
If a Downloader-Transporter job creates a lot of files, increasing partitions and threads allow parallel processing of more files, and can thus improve the performance.
Partition and thread values are typically the same so that a thread is assigned to each partition by batch runtime. If there are more partitions than threads, the batch runtime won't start a partition until a thread is available to run.
Partition and Thread values for the Uploader job can be changed from the "Manage Configurations" tab of the Job Admin GUI. Partition and Thread values can be changed just for an interface module.
The Default value for "item-count" is 1000. It is an attribute of the "chunk" element in the Uploader job xml. The Uploader job reads 1000 records from a file or list of files and then inserts/updates the data in the inbound table.
If performance of an Uploader job is not meeting expectations even after changing partitions and threads, increasing the "item-count" value may improve the performance as it reduces the number of round trips to the database. Memory utilization will increase as you increase the "item-count" value.
