Goals

• Optimize performance of Personas prior to 3.6 launch
• Predict and prepare capacity
• Align with Marketing Plan
• Prepare add-on for post 3.6 scale

Followups From Last Meeting

• Capacity: Gather metrics to predict ramp of Personas demand after 3.6 launch
  • downloads (Suneel)

• Optimization
  • review optimization list (see "Ways to Optimize" below) and 1) add missing items to the list, and 2) indicate bugs assigned for these fixes. (Nightingale)
  • Website code improvements
• Website Cleanup
  • sync up with Nick about resources for code cleanup (see "Ryan suggestions" below) (Morgamic)

Status Update

• Integration (Johnathan Nightingale)
  
• Website Optimization (Mike Morgan)
  
• Marketing (Tara Shahian)
  
• Capacity (Matthew Zeier)
  
• Personas (Suneel Gupta)
  
• AMO (Nick Nguyen)
  

References

Ways to Optimize

• fix server-side components to properly use HTTP headers
• honor HTTP headers properly in the client
  • do not explicitly send no-cache headers for all pages
  • set healthy cache expiry css, jpg, js
  • set healthy cache expiry for persona data
• modify failure or timeout handling in client
  • no network connection - in offline mode it shouldn't even try
  • low timeout - try header first and if no response, keep current persona
  • check cache timeout and if not expired, don't check for new
  • check content-length and if nothing is different, don't download new
• discuss capacity planning assuming the above are addressed
  • if N users updated N times per day, how many requests does that create
  • what hardware would we need to purchase
  • better database server with multiple read-only slaves
  • more memory to support memcache partitions
  • N web nodes for Apache/PHP
  • what software changes would we need to make
  • add memcached support
  • add multiple database support
  • fix session persistence to be efficient in a clustered environment with load balancer

Ryan Suggestions

I feel like we need more resources for getpersonas.com to achieve the level of features, stability and momentum that we're expecting of it. The current backend codebase is relatively messy as it was developed as fast as possible. This is now a technical debt that is gradually slowing us down.

A few solutions come to mind for me:

1. DONE - Ryan is web dev for getpersonas.com Assigning (or hiring) a full-time web developer to getpersonas.com to re-write/fix the codebase (and stay as the full-time developer)
2. Move hosting of personas to AMO

Retrieved from "https://wiki.mozilla.org/Firefox/Projects/Personas_Uplift_Exploration/Capacity"