From 2cb634c373e733273dfd6ceb42858cdd974ca79c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 18 Jul 2022 16:56:31 -0400 Subject: [PATCH] comment --- ..._41ba5600367f6893e8ed0bf01be3d539._comment | 33 +++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 doc/todo/registerurl__58___do_changes_in_journal___34__in_place__34____63__/comment_15_41ba5600367f6893e8ed0bf01be3d539._comment diff --git a/doc/todo/registerurl__58___do_changes_in_journal___34__in_place__34____63__/comment_15_41ba5600367f6893e8ed0bf01be3d539._comment b/doc/todo/registerurl__58___do_changes_in_journal___34__in_place__34____63__/comment_15_41ba5600367f6893e8ed0bf01be3d539._comment new file mode 100644 index 0000000000..0953bd9127 --- /dev/null +++ b/doc/todo/registerurl__58___do_changes_in_journal___34__in_place__34____63__/comment_15_41ba5600367f6893e8ed0bf01be3d539._comment @@ -0,0 +1,33 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 15""" + date="2022-07-18T20:53:29Z" + content=""" +Added the mode that appends without first reading. Enable with +`-c annex.alwayscompact=false`. + +Now some real speed on the benchmark! + +ITER=2000 +Appending, annex.alwayscompact=false: 2.6s + +ITER=4000 +Appending, annex.alwayscompact=false: 2.8s + +ITER=8000 +Appending, annex.alwayscompact=false: 3.14s + +I think annex.alwayscompact=false will be ok for what you're doing +in this case. It's probably not a good idea to set it generally, +although worst case is bloat of the git-annex branch causing slow reads +from it. + +An example of when not to use it is, if you have annex.alwayscommit=false +and annex.alwayscompact=false, and you run git-annex get followed by +git-annex drop, the location log will be larger than it needs to be. Which +does not cause any problem except for slow reads from the git-annex branch, +and will be cleared up by the first update of that log when +annex.alwayscompact=true. + +Still need to implement the atomic appending. +"""]]