diff options
author | Joey Hess <joey@kitenet.net> | 2010-10-25 15:44:27 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2010-10-25 15:44:27 -0400 |
commit | 7fe4bfa20fc9e6ced0b0e933891becb0546b79bb (patch) | |
tree | 265cc61e77127cd6760af52de793787c3467c448 /doc/todo | |
parent | e29210d1dddb79abc0f93fc5175add8e10455688 (diff) |
split commands into 3 phases
I feel like I just leveled up in Haskell.
Diffstat (limited to 'doc/todo')
-rw-r--r-- | doc/todo/parallel_possibilities.mdwn | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/doc/todo/parallel_possibilities.mdwn b/doc/todo/parallel_possibilities.mdwn index 178f95021..15e5171ca 100644 --- a/doc/todo/parallel_possibilities.mdwn +++ b/doc/todo/parallel_possibilities.mdwn @@ -5,9 +5,8 @@ heavily and mostly runs other git commands, maybe not a whole lot. Anyway, each git-annex command is broken down into a series of independant actions, which has some potential for parallelism. -Probably they would need to be split further. Each action currently has 3 -distinct phases, basically "check", "do", and "record". If the check action -returned a do action that returned a record action, then it could easily -make sense to parallelize the check actions and start on the do actions -(which probably won't parallelize well) while they are still being -generated, and possibly parallelize the record actions at the end. +Each action has 3 distinct phases, basically "check", "perform", and +"cleanup". The perform actions are not parellizable; the cleanup may be, +and the check should be easily parallelizable, although they may access the +disk or run minor git query commands, so would probably not want to run +too many of them at once. |