Change Details

//As a Wikisource user, I want the credits information to be cached, so that generation of some ebooks. (in cases when the same book is being generated) is more quick and efficient.// **Background:** Follow-up to T222936. We'd like to eventually cache exported files on disk, but how we go about this will depend on how we implement the job queue (T253283). For now, we can just add simple 10-minute (configurable) caching to the result of requests to phetools/credits.py, which is among the slowest bits. We're likely going to remove the phetools/credits.py dependency (T257886), and when we do the caching can be done on the SQL queries instead. We can use [[ https://symfony.com/doc/current/components/cache.html | Symfony's Cache Component ]], preferably with the APCu adapter in production for best performance. **Examples from Event Metrics:** * https://github.com/wikimedia/eventmetrics/blob/master/src/AppBundle/Repository/Repository.php#L124-L196 * https://github.com/wikimedia/eventmetrics/blob/master/src/AppBundle/Repository/EventWikiRepository.php#L457-L461 * https://github.com/wikimedia/eventmetrics/blob/master/src/AppBundle/Repository/EventWikiRepository.php#L514 **Acceptance criteria:** * Cache requests to phetools/credits.py * Cache adapter should be configurable, default to the file system (use APCu in production) * Cache period should be configurable, default 10 minutes

//As a Wikisource user, I want the credits information to be cached, so that generation of some ebooks. (in cases when the same book is being generated) is more quick and efficient.// **Background:** Follow-up to T222936. We'd like to eventually cache exported files on disk, but how we go about this will depend on how we implement the job queue (T253283). For now, we can just add simple 10-minute (configurable) caching to the result of all API requests (including those to phetools/credits.py, which is among the slowest bits). First we'll want to switch all API requests to use Symfony's HTTP Client ([insert ticket here]), then we can utilizing its [[ https://symfony.com/doc/current/http_client.html#caching-requests-and-responses | built-in caching ]]. **Acceptance criteria:** * Cache all API requests * Cache adapter should be configurable, default to the file system * Cache period should be configurable, default 10 minutes

//As a Wikisource user, I want the credits information to be cached, so that generation of some ebooks. (in cases when the same book is being generated) is more quick and efficient.// **Background:** Follow-up to T222936. We'd like to eventually cache exported files on disk, but how we go about this will depend on how we implement the job queue (T253283). For now, we can just add simple 10-minute (configurable) caching to the result of all API requestssts (including those to phetools/credits.py, which is among the slowest bits. We're likely going to remove the phetools/credits.py dependency (T257886), and when we do the caching can be done onwhich is among the SQL queries insteadslowest bits). We can use [[ https://symfony.com/doc/current/components/cache.html |First we'll want to switch all API requests to use Symfony's Cache Component ]]HTTP Client ([insert ticket here]), preferably with the APCu adapter in production for best performance. **Examples from Event Metrics:** * https://github.com/wikimedia/eventmetrics/blob/master/src/AppBundle/Repository/Repository.php#L124-L196 * https://github.com/wikimedia/eventmetrics/blob/master/src/AppBundle/Repository/EventWikiRepository.php#L457-L461 * https://github.com/wikimedia/eventmetrics/blob/master/src/AppBundle/Repository/EventWikiRepository.php#L514then we can utilizing its [[ https://symfony.com/doc/current/http_client.html#caching-requests-and-responses | built-in caching ]]. **Acceptance criteria:** * Cache requests to phetools/credits.pyall API requests * Cache adapter should be configurable, default to the file system (use APCu in production) * Cache period should be configurable, default 10 minutes