Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: multi-threading while checking out source codes during "repo sync -l" #186

Open
GoogleCodeExporter opened this issue Apr 8, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Assumption: (There are only two parts (-n, -l) of "repo sync" requiring 
multiple CPU cores to use a distributed server system effectively)
repo sync = [repo sync -n] + [repo sync -l]
repo sync -n = “network only”. (Downloading git DB ".git"s)
repo sync -l = “local only”. (Checking out source codes - actual file 
writing)
Please, correct me if I am wrong in some point.

Feature request:
Requesting a feature to enable the parallel CPU process for checking out source 
codes (repo sync -l).  If there is another option to enable the parallel CPU 
process for checking out source codes, we will be able to use our distributed 
server environment more effectively.
If there are other options or ways to support this feature,

Reason for requesting this feature:
repo sync -j option uses multiple CPU cores, but only during "repo sync -n" 
part.  When it processes "repo sync -l" part, it will always use a single core.
Even if we use a wide distributed server environment, there are some 
limitations to use full CPU cores during "repo sync".  With this limitation, 
all we can do is to extend client servers to support more users.

What steps will reproduce the problem?
1.repo init -u https://android.googlesource.com/platform/manifest
2.repo sync
3.See how many CPU cores are being used for each steps ([repo sync -n] + [repo 
sync -l]).

Original issue reported on code.google.com by eric....@lge.com on 11 Nov 2014 at 5:47

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant