From b8694923d9ae2ac83476f971c6d92901507fd695 Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Fri, 24 Dec 2021 18:07:37 -0500 Subject: [PATCH] reduce repo sync jobs due to rate limiting Rate limiting has gotten much more aggressive and using -j32 often triggers it on a fast connection + fast computer. It doesn't appear to happen on most computers, but high end Ryzen machines with a fancy NVMe drive are enough to regular hit the limits making the extra jobs waste more time than they save. --- static/build.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/static/build.html b/static/build.html index 7492b9fb..7b64a4f5 100644 --- a/static/build.html +++ b/static/build.html @@ -339,7 +339,7 @@
mkdir grapheneos-12
 cd grapheneos-12
 repo init -u https://github.com/GrapheneOS/platform_manifest.git -b 12
-repo sync -j32
+repo sync -j16

If your network is unreliable and repo sync fails, you can run the repo sync command again to continue from where it was interrupted. It @@ -368,7 +368,7 @@ cd ../..

Complete the source tree download:

-
repo sync -j32
+
repo sync -j16

The manifest for the latest stable release refers to the revisions in other repositories via commit hashes rather than tag names. This avoids the need to use a @@ -384,7 +384,7 @@ cd ../..

Updating and switching branches or tags

To update the source tree, run the repo init command again to select - the branch or tag and then run repo sync -j32 again. You may need to add + the branch or tag and then run repo sync -j16 again. You may need to add --force-sync if a repository switched from one source to another, such as when GrapheneOS forks an additional Android Open Source Project repository. You don't need to start over to switch between different branches or tags. You may