Use Cache On The API Level Instead Of Fetching The Progress Every Time #30

Closed
opened 2024-12-15 11:33:37 +00:00 by owner · 1 comment
Owner

As the titles says basically. Every time someone calls the API, it has to first talk to the scanner, then return the progress. That's slow, and if there are more clients asking for progress, it could end up making everything slower.

As the titles says basically. Every time someone calls the API, it has to first talk to the scanner, then return the progress. That's slow, and if there are more clients asking for progress, it could end up making everything slower.
owner added the
enhancement
label 2024-12-15 11:33:37 +00:00
owner self-assigned this 2024-12-15 11:33:37 +00:00
Author
Owner

There is also rate limiting functionality in place on the API, but still, if we can just cache the result for like, 30 seconds, that would be great.

There is also rate limiting functionality in place on the API, but still, if we can just cache the result for like, 30 seconds, that would be great.
owner added reference ImplementAPICache 2024-12-19 16:54:03 +00:00
owner closed this issue 2024-12-19 19:29:11 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: owner/RSE#30
No description provided.