This is becoming urgent, because the language differences (short array syntax) will make it increasingly annoying to backport security fixes from WMF production.
Note that we should go ahead and switch to HHVM (T91899) rather than bothering with Zend PHP 5.5.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T91899 Run Payments wiki on HHVM | |||
| Resolved | Ejegg | T138016 Move payments to MediaWiki 1.27 | |||
| Resolved | awight | T130130 [Epic] Upgrade paymentswiki to MediaWiki REL_* release branch or follow the WMF train. Upgrage PHP to HHVM or PHP 5.5 | |||
| Duplicate | Jgreen | T136938 build payments1005 with Debian Jessie, and HHVM or PHP5.5 | |||
| Restricted Task | |||||
| Resolved | Jgreen | T137301 replace payments1001 with new server running debian/jessie | |||
| Resolved | Jgreen | T137299 replace payments1002-1004 with new hardware running debian/jessie | |||
| Resolved | • Cmjohnson | T136881 Rack and setup payments1005-8 | |||
| Unknown Object (Task) | |||||
| Unknown Object (Task) | |||||
| Unknown Object (Task) | |||||
| Restricted Task | |||||
| Resolved | Jgreen | T137298 setup pbuilder jessie instance and build owasp-modsecurity-crs-2.2.9 for jessie | |||
| Resolved | Jgreen | T137434 fundraising jessie build/puppet integration outstanding issues for payments servers |
There is a fairly long chain of dependencies to switch to HHVM, and recent issues in production (T133674, others) make me think we should proceed with caution. Meanwhile we get a bump to php 5.6.17 as we replace payments servers with Jessie hosts. So for the short term I would like to focus on server replacement with Jessie, test and upgrade payments-wiki MW to match core, and then come back to the HHVM question at a later date. Does that sound ok awight?
That would be great! The only additional benefit we might get from HHVM
would be to cut PHP cpu load by 50%, but that can be an optimization for
later. This card is concerned with the breaking language changes, so
Jessie is a perfect solution.
changing to 'normal' priority since it's a tracking task, will leave the dependent tasks as high priority
As of PHP 5.5 (Jessie has 5.6), there is an opcache extension included (only needs to be enabled in config), which caches compiled bytecode in the memory. Together with the other performance improvements since 5.4 (assuming paymentswiki runs on 5.3 now), CPU usage / response time should already decrease without using HHVM (so you get some more headroom before HHVM is really needed).
Closing task because AFAICT it was completed by 9/2016, and there have been no updates since then.