Support/Scaling: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(category -> Support Archive)
 
(5 intermediate revisions by 4 users not shown)
Line 7: Line 7:


*what we need to do
*what we need to do
** Get redirects up and fixed (Thurs. AM) [https://bugzilla.mozilla.org/show_bug.cgi?id=425372] [https://bugzilla.mozilla.org/show_bug.cgi?id=425377]
** Get redirects up and fixed (Thurs. AM) [https://bugzilla.mozilla.org/show_bug.cgi?id=425372] [https://bugzilla.mozilla.org/show_bug.cgi?id=425377] - DONE
** Turn SUMO back on post-peak-time (12pm PST?) [https://bugzilla.mozilla.org/show_bug.cgi?id=425405]
** Turn SUMO back on post-peak-time (12pm PST?) [https://bugzilla.mozilla.org/show_bug.cgi?id=425405] - DONE
** Fix [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Client+Support&product=Sumo&target_milestone=0.6&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&resolution=---&priority=P1&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=Sumo-0.6&query_based_on=Sumo-0.6&field0-0-0=noop&type0-0-0=noop&value0-0-0= P1 bugs in 0.6 list] before b5
** Fix [https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Client+Support&product=Sumo&target_milestone=0.6&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&resolution=---&priority=P1&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=Sumo-0.6&query_based_on=Sumo-0.6&field0-0-0=noop&type0-0-0=noop&value0-0-0= P1 bugs in 0.6 list] before b5


== 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?
*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]
This looks like it will be a Q2 goal.


== Possible outcomes ==
== Possible outcomes ==
* configure NS to cache all sumo links more aggressively (think super-squid)
*<s>configure NS to cache all sumo links more aggressively (think super-squid)</s>
* use squid if necessary
*<s>use squid if necessary</s>
*cron to auto-pull a static version of SUMO landing page from Fx help, point redirects at this static version
*<s>cron to auto-pull a static version of SUMO landing page from Fx help, point redirects at this static version</s>
*cron to auto-pull static versions of all Fx in-product pages as above
*cron to auto-pull static versions of all Fx in-product pages as above
*back out b5 patch to give us more time to test/scale (last resort)
*<s>back out b5 patch to give us more time to test/scale (last resort)</s>
 
[[Category:Support Archive]]

Latest revision as of 09:04, 14 July 2021

Scaling of support.mozilla.com

  • Firefox 3 beta 5 will be replacing in-product help with support.mozilla.com, likely to happen next week (wed/thurs)
    • help will redirect user to sumo front page
    • from there user can click on common articles and tutorials
  • Already having issues this week combined with other complications from release traffic
  • what we need to do
    • Get redirects up and fixed (Thurs. AM) [1] [2] - DONE
    • Turn SUMO back on post-peak-time (12pm PST?) [3] - DONE
    • Fix P1 bugs in 0.6 list before b5

Questions about where we are now

  • 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?

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?
  • 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...)

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? [4]

This looks like it will be a Q2 goal.

Possible outcomes

  • configure NS to cache all sumo links more aggressively (think super-squid)
  • use squid if necessary
  • cron to auto-pull a static version of SUMO landing page from Fx help, point redirects at this static version
  • cron to auto-pull static versions of all Fx in-product pages as above
  • back out b5 patch to give us more time to test/scale (last resort)