mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

followup

Browse source
This commit is contained in:
Joey Hess 2018-10-05 11:33:34 -04:00
parent 292f3a4273
commit 5df65af933
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 17 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

17
doc/todo/config_option_to_use_all_processors_by_default/comment_2_e60a03a8e3225b15424e7e2c505ad133._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2018-10-05T15:26:20Z"
content="""
Just to be clear, not rejecting the idea of -J ncupus out of hand, but I
think it needs some UI consideration. If it were implemented as -J0 (or -J
but I don't think optparse-applicative currently supports -J optionally
lacking a parameter), we might regret it if a better way to determine
a good level of concurrency is later found.
Wanting to run one (or two) concurrent operations per remote is something
that comes to mind as perhaps better in many situations.
Or I can imagine dynamically adjusting concurrency to
optimise throughput. Although I don't know how I'd implement that.
"""]]