aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus@rgdd.se>2025-03-12 13:51:59 +0100
committerRasmus Dahlberg <rasmus@rgdd.se>2025-03-12 14:02:31 +0100
commit528c8b3e606ad9fdb314e41188ed7a0f37488ade (patch)
treed0ea8e36f036b89d6114077a818eeb18f37e6427
parentddc44f9329b9e22115281fd62c5394e534bbc34e (diff)
README: Add note about time to download
The sweet spot to take "all current logs" is right after the last year's log shards expired and were pulled from Google Chrome's list. Because then we don't have 12 months of mostly expired certificates to download. Our measurement was a few months after the sweet spot.
-rw-r--r--README.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/README.md b/README.md
index 5df15df..6300525 100644
--- a/README.md
+++ b/README.md
@@ -88,8 +88,11 @@ Download and verify the logs' Merkle trees up until the current snapshot:
This will take a while depending on the local system, configuration of the
optional `collect` flags, as well as how heavily the logs apply rate-limits.
+
For reference, we [downloaded the logs](./docs/operations.md) from scratch in
-less than 11 days using a single-IP machine that respects the logs' rate-limits.
+less than 11 days using a machine with a single IP address. Note that it would
+take roughly twice as long if the same measurement had been started during the
+fall (because then the current year's log shards would have larger backlogs).
### Assemble