From b9d8c97942aa40b88b3b1623fea8af48a8e05cc1 Mon Sep 17 00:00:00 2001 From: "https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4" Date: Thu, 8 Sep 2016 16:32:08 +0000 Subject: [PATCH] Added a comment: also CPU (on git and git-annex processes) doesn't go to 100% --- ...omment_5_eb7008151a59e35c7850df3a86cf3587._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/todo/make_copy_--fast__faster/comment_5_eb7008151a59e35c7850df3a86cf3587._comment diff --git a/doc/todo/make_copy_--fast__faster/comment_5_eb7008151a59e35c7850df3a86cf3587._comment b/doc/todo/make_copy_--fast__faster/comment_5_eb7008151a59e35c7850df3a86cf3587._comment new file mode 100644 index 0000000000..8fbd3beba8 --- /dev/null +++ b/doc/todo/make_copy_--fast__faster/comment_5_eb7008151a59e35c7850df3a86cf3587._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4" + subject="also CPU (on git and git-annex processes) doesn't go to 100%" + date="2016-09-08T16:32:08Z" + content=""" +seems to wobble around 50% for each one of git and git-annex processes... probably would be an overkill but may be it is easy in haskell (so throwing idea around) if communication was done in async fashion (git-annex wouldn't wait for git to respond but would process its own queue of already returned from git results, while submitting new ones as soon as previous comes out from the --batch). That might make both processes busy to a 100%. + +another idea -- could may be 'annex find' get a -J flag thus starting multiple git ls-files querying processes? + +or both ideas are too overengineered/not tractable? ;) +"""]]