Google Git
Sign in
gerrit / git-repo / refs/heads/stable
commit454fdaf1191c87e5c770ab865a911e10e600e178[log] [tgz]
authorJosip Sokcevic <sokcevic@chromium.org>Mon Oct 07 17:33:38 2024 +0000
committerLUCI <gerrit-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Oct 07 18:44:19 2024 +0000
treea20af3e4f05b48f28d30346648ab9fa1be7f4f64
parentf7f9dd4deb3b92bf175a0411dac60e7b6fdd9cfa [diff]
sync: Always use WORKER_BATCH_SIZE

With 551285fa35ccd0836513e9cf64ee8d3372e5e3f4, the comment about number
of workers no longer stands - dict is shared among multiprocesses and
real time information is available.

Using 2.7k projects as the baseline, using chunk size of 4 takes close
to 5 minutes. A chunk size of 32 takes this down to 40s - a reduction of
rougly 8 times which matches the increase.

R=gavinmak@google.com

Bug: b/371638995
Change-Id: Ida5fd8f7abc44b3b82c02aa0f7f7ae01dff5eb07
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/438523
Commit-Queue: Josip Sokcevic <sokcevic@google.com>
Tested-by: Josip Sokcevic <sokcevic@google.com>
Reviewed-by: Gavin Mak <gavinmak@google.com>
3 files changed
tree: a20af3e4f05b48f28d30346648ab9fa1be7f4f64
  1. .github/
  2. docs/
  3. hooks/
  4. man/
  5. release/
  6. subcmds/
  7. tests/
  8. .flake8
  9. .gitattributes
  10. .gitignore
  11. .gitreview
  12. .isort.cfg
  13. .mailmap
  14. .project
  15. .pydevproject
  16. color.py
  17. command.py
  18. completion.bash
  19. constraints.txt
  20. editor.py
  21. error.py
  22. event_log.py
  23. fetch.py
  24. git_command.py
  25. git_config.py
  26. git_refs.py
  27. git_ssh
  28. git_superproject.py
  29. git_trace2_event_log.py
  30. git_trace2_event_log_base.py
  31. hooks.py
  32. LICENSE
  33. main.py
  34. MANIFEST.in
  35. manifest_xml.py
  36. pager.py
  37. platform_utils.py
  38. platform_utils_win32.py
  39. progress.py
  40. project.py
  41. pyproject.toml
  42. README.md
  43. repo
  44. repo_logging.py
  45. repo_trace.py
  46. requirements.json
  47. run_tests
  48. run_tests.vpython3
  49. setup.py
  50. ssh.py
  51. SUBMITTING_PATCHES.md
  52. tox.ini
  53. wrapper.py
README.md

repo

Repo is a tool built on top of Git. Repo helps manage many Git repositories, does the uploads to revision control systems, and automates parts of the development workflow. Repo is not meant to replace Git, only to make it easier to work with Git. The repo command is an executable Python script that you can put anywhere in your path.

Contact

Please use the repo-discuss mailing list or issue tracker for questions.

You can file a new bug report under the “repo” component.

Please do not e-mail individual developers for support. They do not have the bandwidth for it, and often times questions have already been asked on repo-discuss or bugs posted to the issue tracker. So please search those sites first.

Install

Many distros include repo, so you might be able to install from there.

# Debian/Ubuntu.
$ sudo apt-get install repo

# Gentoo.
$ sudo emerge dev-vcs/repo

You can install it manually as well as it's a single script.

$ mkdir -p ~/.bin
$ PATH="${HOME}/.bin:${PATH}"
$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/.bin/repo
$ chmod a+rx ~/.bin/repo