Proxy selection by monitoring quality and available capacity
Empirical data of exit nodes are continuously monitored and each exit node's overall performance and available capacity are calculated. The empirical data can include monitoring the number of concurrent requests currently being executed by each exit node and the disconnection chronology of each exit node. Further, each exit node is tested by benchmark requests and ping messages and each exit node's quality rate is calculated. Additionally, systems and methods are provided to select an exit node with the highest quality and available capacity value, from a particular pool to route the user request.
1. A method for reporting an available capacity of an exit node to a database and selecting an exit node pool to implement a user request, the method comprising:
reporting, by a proxy supernode, empirical data of an exit node to a first database;
computing, by the proxy supernode, an available capacity value for the exit node, wherein the proxy supernode, upon computing the available capacity value, reports the available capacity value to a second database;
calculating, by the proxy supernode, a success rate for the exit node to determine whether the success rate is higher than a first numerical value assigned to the exit node by a service provider infrastructure;
when the success rate for the exit node is not higher than the first numerical value:
changing, by the proxy supernode, a second numerical value assigned to the exit node by the service provider infrastructure, wherein upon the changing of the second numerical value, the proxy supernode computes a new available capacity value for the exit node and reports the new available capacity value to the second database;
calculating, by the proxy supernode, a quality rate value for the exit node.
2. The method of claim 1 further comprising:
selecting, by the proxy supernode, the exit node by analyzing the available capacity value and the quality rate value, wherein the exit node is used to execute a user request.
3. The method of claim 2 , wherein the available capacity value for the exit node is greater than zero.
4. The method of claim 2 , wherein the exit node executes the user request by gathering data from a target.
5. The method of claim 2 , wherein the exit node, after executing the user request, forwards the data gathered from the target to the proxy supernode.
6. The method of claim 2 , wherein the proxy supernode is connected to the exit node.
7. The method of claim 2 , wherein the proxy supernode forwards the user request to the exit node.
8. The method of claim 1 , wherein the empirical data of the exit node comprises at least one or combination of: disconnection chronology; instances of observed failures; instances of corrupt responses; effective load; pool assignment timestamps; number of user requests executed by the exit node.
9. The method of claim 8 , wherein the disconnection chronology comprises a detailed log of the exit node.
10. The method of claim 9 , wherein the detailed log comprises at least a list of timestamps indicating instances when the exit node connects to the proxy supernode and instances when the exit node disconnects from the proxy supernode.
11. The method of claim 1 , wherein the exit node is in a pool of exit nodes.
12. The method of claim 1 , wherein the success rate is a percentage of success in executing a user request by the exit node.
13. The method of claim 1 , wherein the service provider infrastructure initially assigns the first numerical value to the exit node denoting a minimum tolerance rate for the exit node.
14. The method of claim 13 , wherein the minimum tolerance rate denoted by the first numerical value signifies a minimum tolerated percentage of the success rate.
15. The method of claim 1 , wherein the service provider infrastructure initially assigns the second numerical value to the exit node denoting a maximum capacity of the exit node.
16. The method of claim 15 , wherein the maximum capacity of the exit node signifies the maximum number of user requests that can be executed concurrently by the exit node with a lowest rate of failure.
17. The method of claim 1 , wherein the proxy supernode changes the second numerical value assigned to the exit node such that the success rate is higher than the first numerical value assigned to the exit node.
18. The method of claim 1 , wherein the proxy supernode, after changing the second numerical value assigned to the exit node, stores the second numerical value within memory.
19. The method of claim 1 , wherein the proxy supernode calculates the quality rate value of the exit node using at least one value or combination from: a) time taken by the exit node to perform a benchmark request; b) latency of the exit node; c) probability of disconnection of the exit node during a time frame set by the service provider infrastructure, calculated from the disconnection chronology.
20. The method of claim 1 , wherein the quality rate value for the exit node is represented on a scale of 0-100.
21. The method of claim 1 , wherein the proxy supernode, the first database, and the second database are present within the service provider infrastructure.
22. The method of claim 1 , wherein the proxy supernode continually monitors the exit node.