Currently, the configuration files are requested for every single import. A caching layer with sensible defaults needs to be added, e.g. 1 to 5 minutes.
An ideal solution would be a caching layer that can detect if a configuration file changed, and only then pulls it again.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T140462 Correctly move files from Wikipedia to Commons (2013) | |||
| Resolved | thiemowmde | T146666 Build a commons extension that moves files to Commons | |||
| Resolved | thiemowmde | T193614 Reuse Commonhelper2's config files for category and template matching | |||
| Resolved | Andrew-WMDE | T193615 When a file move is started, find the correct config file for template and category mapping | |||
| Declined | None | T198610 Cache API requests pulling CommonsHelper2 configuration files |
Note we are not aware of a need to even do this. We are tracking the number of imports already. The moment we see these numbers going up significantly, we might need to come back and implement the caching suggested here. Otherwise it's not worth investing time on this, especially because it comes with side effects that can affect the user experience (uploads done very fast might use outdated config pages, and we don't yet know how to avoid this, other than requesting the config page every time).