summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-06-07 21:40:31 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-06-07 21:40:31 -0400
commit4f6b522d8cf25993bc5827b6bbce9b14a1ffdf2d (patch)
tree67bfc5fa4f8bb051873e409d94dea4f42df5e751 /doc
parent109bd9c08b2f7d26720ebb26ed7e165d38accb11 (diff)
update
Diffstat (limited to 'doc')
-rw-r--r--doc/design/assistant/blog/day_4__speed.mdwn1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/design/assistant/blog/day_4__speed.mdwn b/doc/design/assistant/blog/day_4__speed.mdwn
index 151f4af2a..badc6b7b1 100644
--- a/doc/design/assistant/blog/day_4__speed.mdwn
+++ b/doc/design/assistant/blog/day_4__speed.mdwn
@@ -13,6 +13,7 @@ now repeated index writes are eliminated.
... Eliminated too far, it turns out, since it doesn't yet *ever* flush
that queue until shutdown! So the next step here will be to have a worker
thread that wakes up periodically, flushes the queue, and autocommits.
+(This will, in fact, be the start of the [[syncing]] phase of my roadmap!)
There's lots of room here for smart behavior. Like, if a lot of changes are
being made close together, wait for them to die down before committing. Or,
if it's been idle and a single file appears, commit it immediatly, since