![]() ![]() Sample of the output of GIT_TRACE_PERFORMANCE=1 git commit: 18:14:31.949865 trace.c:487 performance: 0.031945775 s: git command: git -git-dir=.git -work-tree=. Size of annexed files in working tree: 2.55 gigabytesīloom filter size: 32 mebibytes (0.4% full) Git annex info (omitting repository info): available local disk space: 146.18 gigabytes (+1 megabyte reserved) Upgrade supported from repository versions: 0 1 2 3 4 5 6 7 Remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav adb tahoe glacier ddar git-lfs httpalso borg hook external Git annex version: git-annex version: 8.20210803-g9cae7c5bbīuild flags: Assistant Webapp Pairing Inotify DBus DesktopNotify TorrentParser MagicMime Feeds Testsuite S3 WebDAVĭependency versions: aws-0.22 bloomfilter-2.0.1.0 cryptonite-0.29 DAV-1.3.4 feed-1.3.2.0 ghc-9.0.2 http-client-0.7.9 persistent-sqlite-2.13.0.3 torrent-10000.1.1 uuid-1.3.15 yesod-1.6.1.2 I posted the output of git annex version and git annex info below in case that is helpful. What should I do next to figure out what the problem is? When searching the web for that git command, I came across this conversation: -content-all/ I posted a sample of the full output below. The time difference between this command and the next is over 1 second, and it seems that git commit is running this type of command many times. literal-pathspecs cat-file '-batch-check=%(objectname) %(objecttype) %(objectsize)' There seems to be one command that git is running that has a non-trivial time difference between other commands, and its 18:14:31.968248 trace.c:487 performance: 247.576906378 s: git command: git -git-dir=.git -work-tree=. To try to get a sense of what is going on, I started by running GIT_TRACE_PERFORMANCE=1 git commit. Those versions might be specific to arch linux, so if that's the case and anybody needs the true versions let me know and I can try to figure out which git-annex commit they are at. After noticing the problem I updated again to package version "8.20210803-81", since I was hoping there might be a fix in the most recent version, but that didn't resolve it. ![]() For an example of how bad the performance is, I first noticed the problem when trying to make a commit, and I waited 20 minutes before cancelling with Ctrl+C. ![]() ![]() I recently did a OS update of all my packages (arch linux), which updated git annex, and now performance is really bad whenever I run git status or git commit in the repo (performance is fine in git repos without git annex). I have been using git annex for several years on this same repo and performance has never been a problem. Hi, if anyone can suggest some steps to take to diagnose a sudden performance problem in my git-annex repo, I'd appreciate it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |