WMF Projects/Upgrade Payments Infrastructure
- 1 Feature justification
- 2 User requirements
- 3 Specification
- 4 Software design document
- 5 Test plan
- 6 Documentation plan
- 7 User interface design docs
- 8 Schedule
- 9 Task management
- 10 Release management plan
- 11 Community management plan
- 12 Notes
Current payment server is not scaling
Be able to serve 100% of our banners with 1click donations at a 3% (best banner) + 2% (variance window)
Upgrade payments server with the following
Software design document
Our goal is to allow for Squid caching of the credit card gateway form and its variants to reduce server load. In order to support this, the software that supports the forms (DonationInterface/payflowpro_gateway extension) will require some rearchitecting.
Use Apache Bench (ab) to determine page load times for the various forms under different load scenarios, with different scaling configurations, compare results to baseline (no LVS/squid/APC) results to determine efficacy.
User interface design docs
None needed yet
- 10/8 - Test APC
APC was not enough to take on the full load of the Jimmy Appeal @ 30% or 60%. Details to follow.
LVS + Memcache
- 10/22 (or 10/29) - Test LVS+Memcache
- Upgrade main payments box to 6core version RT #274
Release management plan
Community management plan
Document lessons learned and coordinate with chapters.