Improve performance of ReadReposMetadata #398

Open
opened 2023-02-02 19:30:08 +00:00 by decentral1se · 0 comments
Owner

E.g. when we abra recipe fetch, we read from all possible pages of the listing of recipes from the Gitea API. However, we might find the recipe in a page (but we currently don't look at each page as we get them) or there might be no new recipes (we don't cache). We could cache and look there, if we don't find anything, scan the entire listing and also check each page along the way. This can have great performance benefits in anything that calls ReadReposMetadata.

E.g. when we `abra recipe fetch`, we read from all possible pages of the listing of recipes from the Gitea API. However, we might find the recipe in a page (but we currently don't look at each page as we get them) or there might be no new recipes (we don't cache). We could cache and look there, if we don't find anything, scan the entire listing and also check each page along the way. This can have great performance benefits in anything that calls `ReadReposMetadata`.
decentral1se added the
enhancement
label 2023-02-02 19:30:08 +00:00
decentral1se added the
abra
label 2023-02-14 07:23:03 +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: coop-cloud/organising#398
No description provided.