devblog/day 550 a plan to finish v6git-annexhttp://git-annex.branchable.com/devblog/day_550__a_plan_to_finish_v6/git-annexikiwiki2019-01-21T15:42:51ZAwesome!http://git-annex.branchable.com/devblog/day_550__a_plan_to_finish_v6/comment_2_4a839c274832e43664d665e90b93146c/michael.hanke2019-01-21T15:42:51Z2018-10-26T17:13:48Z
<p>I have been using V6 more and more over the past weeks, and it is working pretty well for me so far.</p>
<p>If you are now on the final straight, how will parallelization be triggered (i.e. git annex add --jobs ...) when everything runs (or could run) implicitly through the normal Git API.</p>
<p>Thanks for making this happen!</p>
comment 2http://git-annex.branchable.com/devblog/day_550__a_plan_to_finish_v6/comment_2_bae3f3303d61126a337f2dac71681e1d/joey2019-01-21T15:42:51Z2018-10-26T17:41:14Z
<p>Well, <code>git annex add -J</code> works of course.. <code>git add</code> doesn't have a way to
parallelize, nor does git checkout.</p>
<p>It might be useful to parallelize <code>git annex smudge --update</code> which updates
unlocked files in the work tree. I guess it should already be mostly disk
bound when it's copying files and parallalizing that would likely only
worsten things due to seeking (on spinning rust),
but it may have some parallizable overhead when it's making annex.thin hardlinks.
It would need to be controlled via a git config flag or something since
it gets run internally.</p>