Data Throttling
By specifying a priority between 1 and 8, you can throttle the speed at which data is sent to the remote node.
Priorities from 1 to 8 perform data throttling of all send and receive requests. The platform server keeps track of the number of concurrent requests with a node, and extracts all of the defined BPS parameters. Based on the defined priority, the platform server multiply the BPS parameters by the priority, and then divide the product by the number of concurrent tasks to get the speed at which the platform server transmits data.
BPS_TOTAL=56000 BPS_SEND=32000 BPS_RECEIVE=40000If a transfer is running and sending data to node NODEABC. The node definition indicates that you can send 32000 bytes per second, and receive 40000 bytes per second, but you can send and receive only a total of 56000 bytes per second.
If there are currently 5 total tasks running: 3 send and 2 receive tasks. The day is Monday and the time is 6:55 p.m. (18:55 in military time). As you can see from the sample COS entry, when running on Monday at 1855, the priority is set at 5. Therefore, you take the BPS fields in the node definition and multiply them by 100%. Then divide the BPS values by the number of transfers, and get the maximum number of bytes that you can transmit.
BPS_TOTAL=56000*100%/5=11200BPS
BPS_SEND=32000*100%/3=10666BPS
BPS_RECV=48000*100%/2=24000BPS
Because you are sending data, the smaller of the BPS_SEND and BPS_TOTAL numbers is used. In this case, you can send a maximum of 10666BPS. If the number of transfers changes, the platform server recompute the maximum BPS on each packet sent.
If the transfer runs long enough and that the current time becomes 7 p.m. (1900 in military time). As the sample COS entry shows, the priority becomes 9 for this entry. A priority of 9 indicates an unlimited transfer speed. Therefore, the platform server transmits data as fast as possible to node NODEABC.