This commit is contained in:
Joey Hess 2024-08-12 09:43:14 -04:00
parent 1265d7e5df
commit bcd2b9a5c4
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 20 additions and 0 deletions

View file

@ -41,6 +41,23 @@ always contain hashe. Also, including the concacenation of all the UUIDs
of reposotories in the group makes it harder to generate a combination of
key and repository UUID that makes that repository want to contain the key.
## size balancing
Beyond filtering balanced repos to those that have enough free space to
store a key, the sizes of the repos can be used in other ways.
If the maximum size of all the balanced repos is known, they can be filled
with data proportional to their sizes.
If the maximum size is not known of any balanced repos, a reasonable thing
to do would be to assume they all have the same maximum size, and fill them
proportionally also.
If the maximum size of some but not others is known, what then?
Balancing this way would fall back to the method above when several repos
are equally good candidates to hold a key.
## stability
Note that this preferred content expression will not be stable. A change in

View file

@ -45,6 +45,9 @@ Planned schedule of work:
Also note that "fullybalanced=foo:2" is not currently actually
implemented!
* implement size-based balancing, either as the default or as another
preferred content expression.
* `git-annex info` can use maxsize to display how full repositories are
* balanced= and fullybalanced= need to limit the set of repositories to