86
edits
(Created page with 'Meeting on 9/21/09 Notes Goals for Capacity Planning: 1. Take a data-driven approach to predicting load after 3.6 launch 2. Optimize site to better handle load 1. Take a data-d…') |
No edit summary |
||
Line 5: | Line 5: | ||
1. Take a data-driven approach to predicting load after 3.6 launch | 1. Take a data-driven approach to predicting load after 3.6 launch | ||
2. Optimize site to better handle load | 2. Optimize site to better handle load | ||
3. Clean up getpersonas.com code in time for 3.6 launch | |||
--- | |||
1. Take a data-driven approach to predicting load after 3.6 launch | 1. Take a data-driven approach to predicting load after 3.6 launch | ||
Line 37: | Line 40: | ||
+ add multiple database support | + add multiple database support | ||
+ fix session persistence to be efficient in a clustered environment with lead balancer | + fix session persistence to be efficient in a clustered environment with lead balancer | ||
3. Clean up getpersonas.com code in time for 3.6 launch | |||
Next Steps: morgamic to sync up with Nick about resources for code cleanup | |||
Excerpt from note from Ryan with concerns: | |||
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) 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 |
edits