followup
This commit is contained in:
parent
292f3a4273
commit
5df65af933
1 changed files with 17 additions and 0 deletions
|
@ -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.
|
||||
"""]]
|
Loading…
Add table
Reference in a new issue