11cc9f1933
Factored out overLocationLogs from CmdLine.Seek, which can calculate this pretty fast even in a large repo. In my big repo, the time to run git-annex info went up from 1.33s to 8.5s. Note that the "backend usage" stats are for annexed files in the working tree only, not all annexed files. This new data source would let that be changed, but that would be a confusing behavior change. And I cannot retitle it either, out of fear something uses the current title (eg parsing the json). Also note that, while time says "402108maxresident" in my big repo now, up from "54092maxresident", top shows the RES constant at 64mb, and it was 48mb before. So I don't think there is a memory leak. I tried using deepseq to force full evaluation of addKeyCopies and memory use didn't change, which also says no memory leak. And indeed, not even calling addKeyCopies resulted in the same memory use. Probably the increased memory usage is buffering the stream of data from git in overLocationLogs. Sponsored-by: Brett Eisenberg on Patreon |
||
|---|---|---|
| .. | ||
| GitAnnex | ||
| GitAnnexShell | ||
| Action.hs | ||
| AnnexSetter.hs | ||
| Batch.hs | ||
| GitAnnex.hs | ||
| GitAnnexShell.hs | ||
| GitRemoteTorAnnex.hs | ||
| Option.hs | ||
| Seek.hs | ||
| Usage.hs | ||