mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

further thought

Browse source
This commit is contained in:
Joey Hess 2019-03-28 15:46:14 -04:00
parent a53c2a7e13
commit c68ae14268
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 6 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/todo/inneficiency_on_slow_filesystems_opening_nonexistant_journal_files.mdwn
View file

@ -26,6 +26,12 @@ So, this optimisation seems it would be limited to commands that
are not in batch mode and do strictly read-only queries. Which seems a bit are not in batch mode and do strictly read-only queries. Which seems a bit
hard to plumb through to the git-annex branch reading code. hard to plumb through to the git-annex branch reading code.
> Unless, perhaps, we can rely on the process that modifies the git-annex
> branch having cleanly exited, and so committed its changes to the branch,
> before the next batch query. Can we rely on that, or might a batch
> mode command expect to see changes made up to the point it started
> by a concurrent command?
An easier alternative would be an option that bypasses reading the journal. An easier alternative would be an option that bypasses reading the journal.
But maybe there's some other, better way to avoid this slow case? But maybe there's some other, better way to avoid this slow case?
--[[Joey]] --[[Joey]]