Adjusting communications parameters based on known characteristics
US-10764168-B1 · Sep 1, 2020 · US
US12058056B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-12058056-B1 |
| Application number | US-202117338089-A |
| Country | US |
| Kind code | B1 |
| Filing date | Jun 3, 2021 |
| Priority date | Apr 16, 2014 |
| Publication date | Aug 6, 2024 |
| Grant date | Aug 6, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods for providing web service instances to support traffic demands for a particular web service in a large-scale distributed system are disclosed. An example method includes determining a peak historical service load for the web service. The service load capacity for each existing web service instance may then be determined. The example method may then calculate the remaining service load after subtracting the sum of the service load capacity of the existing web service instances from the peak historical service load for the web service. The number of web service instances necessary in the large-scale distributed system may be determined based on the remaining service load. The locations of the web service instances may be determined and changes may be applied to the large-scale system based on the number of web service instances necessary in the large-scale distributed system.
Opening claim text (preview).
The invention claimed is: 1. A method for managing capacity of web service instances running on a computing system, comprising: determining, a number of web service instances required to support a web service, based on traffic load data associated with the web service and a service load capacity for one or more existing web service instances of the web service; allocating a given number of web service instances to the web service based on a number of web service requests for the web service and the number of web service instances determined to be required to support the web service; and assigning, the given number of web service instances allocated, to one or more datacenter cells based on around trip latency between a first set of computers originating the number of web service requests and the one or more datacenter cells for processing the given number of web service instances and on locations of other one or more datacenter cells at which other web service instances required to support the web service are run. 2. The method of claim 1 , wherein the assigning comprises analyzing historical service load data associated with the web service to determine physical origins of web service traffic associated with the web service. 3. The method of claim 2 , wherein the assigning comprises determining a total service load for the web service. 4. The method of claim 1 , wherein the round trip latency used for assigning the given number of web services instances allocated to the one or more datacenter cells is dependent on a given web service. 5. A system for managing capacity of web service instances running on a computing system, comprising: one or more processing devices; and one more storage devices storing instructions that, when executed by the one or more processing devices cause the one or more processing devices to: determine a number of web service instances required to support a web service based on traffic load data associated with the web service and a service load capacity for one or more existing web service instances of the web service; allocate a given number of web service instances to the web service based on a number of web service requests for the web service and the number of web service instances determined to be required to support the web service; and assign, the given number of web service instances allocated, to one or more datacenter cells based on a round trip latency between a first set of computers originating the number of web service requests and the one or more datacenter cells for processing the given number of web service instances and on locations of other one or more datacenter cells at which other web service instances required to support the web service are run. 6. The system of claim 5 , wherein to cause the one or more processing devices to assign comprises analyzing historical service load for the web service to determine physical origins of web service traffic associated with the web service. 7. The system of claim 6 , wherein the assigning comprises determining a total service load for the web service. 8. The system of claim 5 , wherein the round trip latency used for assigning the given number of web services instances allocated to the one or more datacenter cells is dependent on a given web service.
for accessing one among a plurality of replicated servers · CPC title
wherein the managed service relates to web hosting · CPC title
Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components · CPC title
Techniques for rebalancing the load in a distributed system · CPC title
by balancing the load, e.g. traffic engineering · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.