Support/Scaling

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
• what we've done
  • disable session auto-start
  • verify that NS is caching pages for SUMO
• what we need to do
  • profile app (today/tomorrow, morgamic/nelson)
  • add memcache support (nelson)
  • set up custom NS rules to cache more aggresively (?)
  • load test in next 8-9 days for b5 (quick/dirty) (oremj/morgamic)
  • load test in April for Fx3 (more extensive) (people)

Questions about where we are now

• how many boxes serve up sumo?
• how many databases are used by sumo?
• is it possible to adjust NS cache rules to be more squid-like so entries don't randomly expire?

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)