Confirmed users
632
edits
Loop/Load Handling: Difference between revisions
Jump to navigation
Jump to search
→Simple Push Server Load Distribution
| Line 69: | Line 69: | ||
== Simple Push Server Load Distribution == | == Simple Push Server Load Distribution == | ||
See {{Bug|1055139}}. | See {{Bug|1055139}} and {{Bug|1055143}}. | ||
Currently, the push servers have been measured to handle up to 5 million users per cluster. With potentially several hundred million users ultimately using the Loop service, we need the ability to scale to use multiple simple push clusters. | |||
To support this behavior, the Loop client will query the Loop server for the address of the Simple Push server to use, rather than using the Simple Push server configured in the client prefs. The loop server will maintain a list of Simple Push clusters, and hand out a random entry from this list each time a client requests the address of a Simple Push server. In this way, we can bring additional Simple Push servers online to accommodate the load required to support the Loop service. | |||
== Simple Push Server Load Reduction == | == Simple Push Server Load Reduction == | ||
See {{Bug|1060610}}. | See {{Bug|1060610}}. | ||