Improve performance of ReadReposMetadata #398
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#398
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 callsReadReposMetadata
.3wordchant referenced this issue2024-02-10 21:37:50 +00:00
decentral1se referenced this issue2024-03-27 06:43:37 +00:00