Abstract: Certain example embodiments relate to techniques for addressing resource utilization issues in network components (e.g., file transfer servers running out of memory, for example) by identifying and predicting scenarios that are likely to cause problems, and handling them gracefully, without having to deny service completely. Based on current runtime status information and a prediction of how a given request will impact the server and/or the network, a determination is made regarding whether that request is to be accepted by the server. If the total resource usage of the server exceeds or is likely to exceed a threshold: the speed at which requests being processed are being handled is controlled, such that (a) speeds of all but some of the requests are throttled, (b) throttled requests are neither terminated nor allowed to timeout, (c) as non-throttled requests are completed, requests that are throttled have their speeds increased in a predetermined manner.

Abstract: Certain example embodiments relate to techniques for addressing resource utilization issues in network components (e.g., file transfer servers running out of memory, for example) by identifying and predicting scenarios that are likely to cause problems, and handling them gracefully, without having to deny service completely. Based on current runtime status information and a prediction of how a given request will impact the server and/or the network, a determination is made regarding whether that request is to be accepted by the server. If the total resource usage of the server exceeds or is likely to exceed a threshold: the speed at which requests being processed are being handled is controlled, such that (a) speeds of all but some of the requests are throttled, (b) throttled requests are neither terminated nor allowed to timeout, (c) as non-throttled requests are completed, requests that are throttled have their speeds increased in a predetermined manner.