Confirmed users
632
edits
Loop/Load Handling: Difference between revisions
Jump to navigation
Jump to search
→Recommended Handling: Added list of servers of interest
m (→Recommended Handling: typo) |
(→Recommended Handling: Added list of servers of interest) |
||
| Line 86: | Line 86: | ||
''If you'd like to keep an eye on the throttle without having to jump through several hoops, you can install [https://dl.dropboxusercontent.com/u/53717247/loopthrottle-0.0.1.xpi the simple Firefox and Thunderbird Add-On] that I created to keep tabs on the value. It's a bit of a hack, in that it requires you to drag the display out of the customize palette to whereever you want it to be, and then to restart the browser before it starts working.'' | ''If you'd like to keep an eye on the throttle without having to jump through several hoops, you can install [https://dl.dropboxusercontent.com/u/53717247/loopthrottle-0.0.1.xpi the simple Firefox and Thunderbird Add-On] that I created to keep tabs on the value. It's a bit of a hack, in that it requires you to drag the display out of the customize palette to whereever you want it to be, and then to restart the browser before it starts working.'' | ||
=== Servers to Watch === | |||
When in production, we should check on the health of the following servers before increasing the throttle, and use their state to determine how much we're comfortable increasing the value: | |||
* Loop Server (load, database size) | |||
* FxA server (load) | |||
* Simple Push server (load, connection count) | |||
* TokBox infrastructure (actual servers and metrics to be determined by TokBox) | |||
== Simple Push Server Load Distribution == | == Simple Push Server Load Distribution == | ||