Improve performance of ReadReposMetadata #398

New Issue

decentral1se · 2023-02-02T19:30:08Z

decentral1se commented

2023-02-02 19:30:08 +00:00

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`.

👍 1

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

~~3wordchant referenced this issue 2024-02-10 21:37:50 +00:00~~

Support non-TLD resolving / IP HostNames #566

~~decentral1se referenced this issue 2024-03-27 06:43:37 +00:00~~

`abra` v0.10.x-beta release planning #583

Sign in to join this conversation.