SYSTEM AND METHOD FOR DYNAMIC QUEUE MANAGEMENT USING QUEUE PROTOCOLS
First Claim
1. A computer-implemented method for predicting future system loads by weighting previous request loads for resources, the method comprising:
- accessing, at a load management server, one or more data sources;
querying the one or more data sources for system load data including a first request load and a second request load, the first request load representing a first rate of first query requests for a resource, the second request load representing a second rate of second query requests for the resource, the first query requests occurring during a first time period, and the second query requests occurring during a second time period;
identifying each of a first attribute associated with the first time period and a second attribute associated with the second time period, each of the first attribute and the second attribute corresponding to a characteristic of the resource;
identifying each of a first weight corresponding to the first attribute and a second weight corresponding to the second attribute;
determining a future request load on the one or more data sources, the future request load predicting a load of third query requests to occur during a third time period, the third time period being in the future, and the determination of the future request load being based on at least one of the first weight or the second weight; and
identifying a parameter to associate with the resource for the duration of the third time period occurring in the future.
3 Assignments
0 Petitions
Accused Products
Abstract
A system and method for efficiently processing and managing data stored in a queue. A processing device may process the data stored in the queue. Queue protocols can be applied to the queue to efficiently process and manage data stored in the queue. Queue protocols may facilitate efficient use of processing resources that process the data stored in one or more queues. A queue protocol may include at least a first protocol for facilitating transfer of data in the queue to another queue processed by another processing device or a second protocol for inhibiting transfer of data in the queue to another queue.
-
Citations
20 Claims
-
1. A computer-implemented method for predicting future system loads by weighting previous request loads for resources, the method comprising:
-
accessing, at a load management server, one or more data sources; querying the one or more data sources for system load data including a first request load and a second request load, the first request load representing a first rate of first query requests for a resource, the second request load representing a second rate of second query requests for the resource, the first query requests occurring during a first time period, and the second query requests occurring during a second time period; identifying each of a first attribute associated with the first time period and a second attribute associated with the second time period, each of the first attribute and the second attribute corresponding to a characteristic of the resource; identifying each of a first weight corresponding to the first attribute and a second weight corresponding to the second attribute; determining a future request load on the one or more data sources, the future request load predicting a load of third query requests to occur during a third time period, the third time period being in the future, and the determination of the future request load being based on at least one of the first weight or the second weight; and identifying a parameter to associate with the resource for the duration of the third time period occurring in the future. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A system, comprising:
-
one or more data processors; and a non-transitory computer-readable storage medium containing instructions which, when executed on the one or more data processors, cause the one or more data processors to perform operations including; accessing, at a load management server, one or more data sources; accessing, at a load management server, one or more data sources; querying the one or more data sources for system load data including a first request load and a second request load, the first request load representing a first rate of first query requests for a resource, the second request load representing a second rate of second query requests for the resource, the first query requests occurring during a first time period, and the second query requests occurring during a second time period; identifying each of a first attribute associated with the first time period and a second attribute associated with the second time period, each of the first attribute and the second attribute corresponding to a characteristic of the resource; identifying each of a first weight corresponding to the first attribute and a second weight corresponding to the second attribute; determining a future request load on the one or more data sources, the future request load predicting a load of third query requests to occur during a third time period, the third time period being in the future, and the determination of the future request load being based on at least one of the first weight or the second weight; and identifying a parameter to associate with the resource for the duration of the third time period occurring in the future. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A computer-program product tangibly embodied in a non-transitory machine-readable storage medium, including instructions configured to cause a data processing apparatus to perform operations including:
-
accessing, at a load management server, one or more data sources; querying the one or more data sources for system load data including a first request load and a second request load, the first request load representing a first rate of first query requests for a resource, the second request load representing a second rate of second query requests for the resource, the first query requests occurring during a first time period, and the second query requests occurring during a second time period; identifying each of a first attribute associated with the first time period and a second attribute associated with the second time period, each of the first attribute and the second attribute corresponding to a characteristic of the resource; identifying each of a first weight corresponding to the first attribute and a second weight corresponding to the second attribute; determining a future request load on the one or more data sources, the future request load predicting a load of third query requests to occur during a third time period, the third time period being in the future, and the determination of the future request load being based on at least one of the first weight or the second weight; and identifying a parameter to associate with the resource for the duration of the third time period occurring in the future. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification