1,107
edits
Support/Scaling: Difference between revisions
→Questions about where we are now
| Line 13: | Line 13: | ||
== Questions about where we are now == | == Questions about where we are now == | ||
*how many boxes serve up sumo? | *how many boxes serve up sumo? | ||
We are at 8 boxes. It is on the PHP5 cluster though so these are shared boxes with most of the applications that we run. | |||
*how many databases are used by sumo? | *how many databases are used by sumo? | ||
Two databases - mrdb80, mrdb81. Although from my inspections it seems that sumo ONLY uses the master (mrdb80) and has no ability to scale on slaves. (See https://bugzilla.mozilla.org/show_bug.cgi?id=426253) | |||
*is it possible to adjust NS cache rules to be more squid-like so entries don't randomly expire? | *is it possible to adjust NS cache rules to be more squid-like so entries don't randomly expire? | ||
*has there been a noticeable performance difference after the recent optimizations? | *has there been a noticeable performance difference after the recent optimizations? | ||
*what's currently the bottleneck? (ex: number of hits to the database, the queries we're running, PHP execution...) | *what's currently the bottleneck? (ex: number of hits to the database, the queries we're running, PHP execution...) | ||
Previous bottleneck was requests to the netapp - this has now been fixed by serving pages from local disk. This took page load times from 14s to 0.5s on average. | |||
*what would be involved in upgrading to MySQL 5? [https://bugzilla.mozilla.org/show_bug.cgi?id=425135#c4] | *what would be involved in upgrading to MySQL 5? [https://bugzilla.mozilla.org/show_bug.cgi?id=425135#c4] | ||
This looks like it will be a Q2 goal. | |||
== Possible outcomes == | == Possible outcomes == | ||