analysis

diff --git a/doc/bugs/many___40__2x_jobs__63____41___sleeping__hash-object__processes__63__/comment_1_c01d8d2e4aa2cb0d064ab223e615a75c._comment b/doc/bugs/many___40__2x_jobs__63____41___sleeping__hash-object__processes__63__/comment_1_c01d8d2e4aa2cb0d064ab223e615a75c._comment
new file mode 100644 (file)
index 0000000..bd3256f
--- /dev/null
+++ b/doc/bugs/many___40__2x_jobs__63____41___sleeping__hash-object__processes__63__/comment_1_c01d8d2e4aa2cb0d064ab223e615a75c._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2022-07-25T20:37:55Z"
+ content="""
+I was able to reproduce this by feeding 10 urls into git-annex addurl
+-J5 and got 7 hash-object processes running.
+
+filter.annex.process has nothing to do with this. I reproduced the behavior
+without it set.
+
+Seems like a simple concurrency issue, where each thread potentially starts
+its own hash-object handle, and there can be around 2x as many threads
+started as the -J number due to job stages. Annex.Concurrent sets up pools of
+handles for other similar git processes, but not hash-object.
+"""]]