aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus@rgdd.se>2025-03-12 19:00:40 +0100
committerRasmus Dahlberg <rasmus@rgdd.se>2025-03-12 19:00:40 +0100
commitf699da3d286a5b840a7a7b7c5f5e0b54f651a03e (patch)
tree4d1bcbdea4f5eec49d2f983de47cb06d29b14d17
parented900e7590010dec73209e3b8d27d07f91541c38 (diff)
README: Shorten down
How long it takes ages poorly since rate limit configurations change; and it is hard to tell if we encountered any 429s, see timeline [9].
-rw-r--r--README.md8
1 files changed, 2 insertions, 6 deletions
diff --git a/README.md b/README.md
index a6f67f1..0eca396 100644
--- a/README.md
+++ b/README.md
@@ -87,12 +87,8 @@ Download and verify the logs' Merkle trees up until the current snapshot:
Trust Asia Log2024-2 | 246.2 entries/s | Estimated done in 0.11 hours | Working on [17664, 112771)
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 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).
+optional `collect` flags, as well as how heavily the logs apply rate-limits. If
+you are not bandwidth constrained, consider increasing the worker count (`-w`).
### Assemble