Batch retrieval of download counts with /api/download_counts #401
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
CKAN queries SpaceDock for download counts every day. Currently this happens via the
/api/mod/<mod_id>
route, which means that for each SpaceDock mod that CKAN knows about, we do:This isn't a big problem today, but it is mildly wasteful of resources that could otherwise be available for users.
Changes
Now a new
/api/download_counts
route is available that takes multiplemod_id
form parameters as input, then runs one SQL query that returns the download counts for all the mods without extraneous info and returns them as one JSON object.To test locally:
Once this is live, KSP-CKAN/NetKAN-Infra#228 will allow download counts to be queried with just one HTTPS and SQL request per day.