From 8617444de8c5281fd8ba8bb891a4f28fc5dfcf6f Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 26 Feb 2013 16:31:46 -0400 Subject: typo --- .../comment_1_d350c39c67031c500e3224e92c0029ea._comment | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_1_d350c39c67031c500e3224e92c0029ea._comment b/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_1_d350c39c67031c500e3224e92c0029ea._comment index 092a7bbf2..f8b7e789b 100644 --- a/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_1_d350c39c67031c500e3224e92c0029ea._comment +++ b/doc/bugs/added_branches_makes___39__git_annex_unused__39___slow/comment_1_d350c39c67031c500e3224e92c0029ea._comment @@ -14,6 +14,6 @@ Another optimisation is to only check each git ref once, even if multiple branch Indeed, if you go on and add 100 identical branches, you'll find it runs in just about the same time it ran with 2 branches. (There's a little overhead in getting the list of branches and throwing out the duplicates, but that's all.) -What then explains your numbers? Well, I have no idea. I cannot replicate them; I tend to see about the same amount of time taken with two duplicate branches as with one branch. I suspect you just didn't get statistically valid results, which playing around with `sleep` at the command line often doesn't, +What then explains your numbers? Well, I have no idea. I cannot replicate them; I tend to see about the same amount of time taken with two duplicate branches as with one branch. I suspect you just didn't get statistically valid results, which playing around with `time` at the command line often doesn't, due to caching, other active processes, etc. """]] -- cgit v1.2.3