Abstract: Examples described herein relate to determining the waiting period using an agent. Examples include a source device transmitting a request to a target device to perform an action and waiting for a response to the request for an expected waiting period. Examples include an agent to detect an event at the target device and notify the source device to abort the request. The agent may determine an adjusted waiting period for completion of the action due to the event. For a new request, the source device may wait for a period corresponding to the adjusted waiting period.

Abstract: Examples described herein relate to method and system for determining a response time for an action. A request for an action may be communicated from a source entity to a target entity. The action is generated by the source entity and which is to be responded by the target entity. Further, a response time corresponding to the action may be determined based on prior execution experience of one or more jobs associated with the action and a learning rate. Thereafter, the source entity may be allowed to wait for a response corresponding to a completion of the action from the target entity for at least a time duration corresponding to the response time.

Abstract: Examples described herein relate to method and system for determining a response time for an action. A request for an action may be communicated from a source entity to a target entity. The action is generated by the source entity and which is to be responded by the target entity. Further, a response time corresponding to the action may be determined based on prior execution experience of one or more jobs associated with the action and a learning rate. Thereafter, the source entity may be allowed to wait for a response corresponding to a completion of the action from the target entity for at least a time duration corresponding to the response time.

Abstract: Examples disclosed herein relate to a mechanism for dynamically adjusting wait time values. Some disclosed examples enable transmitting, by a source entity, a request for an action to a target entity. The action may be generated by the source entity. Some examples enable identifying a first wait time value for the source entity that indicates an amount of time that the source entity is allowed to wait for a response from the target entity between the transmission of the request and a timeout state. Some examples may enable dynamically adjusting the first wait time value based on an entity specification of the source or target entity to generate a second wait time value. Some examples may enable allowing the source entity to wait for the response from the target entity for at least the amount of time indicated in the second wait time value.

Abstract: Examples disclosed herein relate to a mechanism for dynamically adjusting wait time values. Some disclosed examples enable transmitting, by a source entity, a request for an action to a target entity. The action may be generated by the source entity. Some examples enable identifying a first wait time value for the source entity that indicates an amount of time that the source entity is allowed to wait for a response from the target entity between the transmission of the request and a timeout state. Some examples may enable dynamically adjusting the first wait time value based on an entity specification of the source or target entity to generate a second wait time value. Some examples may enable allowing the source entity to wait for the response from the target entity for at least the amount of time indicated in the second wait time value.

Abstract: A software module on a client computer sends a query to a remote computer server operating a cloud service and receives a response, in order to determine latency. The latency is used with the total size of the packets sent and the packet size to determine the bandwidth available over the network connection at that time. Bandwidth available is calculated periodically and stored in a database of the client computer. Comparing a calculated bandwidth with predefined threshold values indicates whether the network status is good for initiating a cloud service with the computer server or poor. Any number of bandwidth available values are used to determine a slope and the slope is used to predict a bandwidth available value at a future time. A bandwidth available moving average is calculated by summing the bandwidth values for the previous days and dividing by the number of days; the moving average is calculated periodically.