|Bookshelf Home | Contents | Index | PDF|
The following three examples show how the assignment administrator might use threshold, batch size, and load splitter configuration to split a batch request into multiple, manageable tasks. You may use this feature differently, depending on your business model for Siebel Assignment Manager.
In this example, the load splitter receives 900 row IDS for the account assignment object. Because this is less than the threshold, which is 1000, no load splitting occurs. All rows are passed to the server with the lowest priority number.
In this example, the load splitter receives 1001 row IDs for the account assignment object, which is greater than the threshold of 1000. The total number of tasks is 10, and minimum batch size is 500. The load splitter tries to split the rows into even tasks. The default calculation for batch size calculates 1001 divided by 10, or about 100 rows, as the batch size. Due to the ramp-up time for different server components, this processing is actually more inefficient than just running two separates batches of 500 and 501 row IDs. Therefore, the load splitter takes the minimum batch size of 500 into account and splits the rows into two tasks of 500 and 501.
In this example, the load splitter receives 6023 row IDs for the Account assignment object. Because this is greater than the threshold of 1000, the load splitter tries to split the rows into batches. The default calculation for batch size calculates 6023 divided by 10, or about 600 rows, as the batch size. Because this is greater than the minimum batch size of 500, the load splitter splits the rows into 8 tasks of 600 and one task of 623.
|Siebel Assignment Manager Administration Guide||Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.|