Skip to content

Commit af5c9bd

Browse files
Merge pull request #74 from lukpueh/fix-metadata-calc
Update metadata calc in text after removing sha256
2 parents 8b17d9f + e3a993c commit af5c9bd

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

pep-0458.txt

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -554,9 +554,9 @@ split all targets in the *bins* role by delegating them to 16,384
554554
*bin-n* roles (see C10 in Table 2). Each *bin-n* role would sign
555555
for the PyPI targets whose SHA2-512 hashes fall into that bin
556556
(see and Figure 2 and `Consistent Snapshots`_). It was found
557-
that this number of bins would result in a 6-10% metadata overhead
557+
that this number of bins would result in a 5-9% metadata overhead
558558
(relative to the average size of downloaded distribution files; see V13 and
559-
V15 in Table 3) for returning users, and a 70% overhead for new
559+
V15 in Table 3) for returning users, and a 69% overhead for new
560560
users who are installing pip for the first time (see V17 in Table 3).
561561

562562

@@ -590,7 +590,7 @@ A few assumptions used in calculating these metadata overhead percentages:
590590
| C10 | # of bins | 16,384 |
591591
+------+--------------------------------------------------+-----------+
592592

593-
C8 by computed querying the number of release files.
593+
C8 was computed by querying the number of release files.
594594
C9 was derived by taking the average between a rough estimate of the average
595595
size of release files *downloaded* over the past 31 days (1,628,321 bytes),
596596
and the average size of releases files on disk (2,740,465 bytes).
@@ -645,8 +645,8 @@ __ https://docs.google.com/spreadsheets/d/11_XkeHrf4GdhMYVqpYWsug6JNz5ZK6HvvmDZX
645645

646646
This number of bins SHOULD increase when the metadata overhead for returning
647647
users exceeds 50%. Presently, this SHOULD happen when the number of targets
648-
increase at least 8x from over 2M to over 18M, at which point the metadata
649-
overhead for returning and new users would be around 46-51% and 111%
648+
increase at least 10x from over 2M to over 22M, at which point the metadata
649+
overhead for returning and new users would be around 50-54% and 114%
650650
respectively, assuming that the number of bins stay fixed. If the number of
651651
bins is increased, then the cost for all users would effectively be the cost
652652
for new users, because their cost would be dominated by the (once-in-a-while)

0 commit comments

Comments
 (0)