APCu is apparently faster and the Symfony recommendation. Furthermore we apparently can't connect to Toolforge's Redis from the VPS instances, so we'd have to create our own Redis server anyway.
The Symfony cache component should be used in the event we switch backends at a later time.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | MusikAnimal | T206495 Standardize navigation and adjust naming of pages | |||
| Resolved | Samwilson | T213470 Implement UX for Updating and Downloading | |||
| Resolved | Samwilson | T206576 Create new UI elements: ‘Download report’ menu, 'Popup format selector', Animated 'Working' Indicator' | |||
| Invalid | • Prtksxna | T207911 Inform users as to whether Updating is currently allowed or blocked | |||
| Resolved | MusikAnimal | T192954 Add cronjob to regularly spawn any unstarted jobs that have been submitted to the queue | |||
| Resolved | MusikAnimal | T206180 Create Event Metrics VPS and move Grant Metrics to it | |||
| Resolved | MusikAnimal | T208818 Use APCu cache adapter instead of Redis |
Self-merged so we could use the "Edit list" (formerly "revision browser" or "all data" page) on the VPS instances. We can make more changes to the caching system as needed.