git/list[1] front-page[2] threads[3] people[4] search[5] about
 

"git commit" of single file takes 5 minutes, mounted fileystem/diskimage with 50G GIT repo + 900G of builds articles

From
SSSaravanan Shanmugham (sarvi) <sarvi@cisco.com>
Date
Aug 26, 2019, 20:43 UTC
Message-ID
<7A1C0468-E07D-4D10-8891-01AC1FA1CC1B@cisco.com>
Based on a previous thread “First Git status takes 40+ minutes, when mounting fileystem/diskimage with 50G GIT repo + 900G of builds articles”
The context is that 
  1. git wokspace was clone(50G)
  2. some 30 platorms build(900G)
  3. This tree was then copied into a new diskimage/filesystem + git update-index --refresh" was done to update the index to the new filesystem, then frozen.
  4. New workspaces created by cloning this frozen diskimage(< 30 seconds)
  5. This diskimage was mounted on a new machine
  6. A file was modified and "git add/commit" was done

I have done “git update-index –refresh”, in the mounted filesystem, as above This has improved “git status/diff” timing from 40+ minutes to 1.5 minutes for the first time and <5 seconds for subsequent calls.

But "git commit -m "dummy commit" of a 1 line change in 1 file takes about 5-6 minutes, everytime in this workspace. Tracing shows a whole bunch. The entire 5-6 minutes worth of the following sort of trace logs. 3:13:50.320930 trace git-lfs: filepathfilter: rejecting "x/y/z.o.command" via [] 13:13:50.320940 trace git-lfs: filepathfilter: accepting " x/y/z.o.command " 13:13:50.320862 trace git-lfs: filepathfilter: rejecting "a/b/c/d.o.command" via [] 13:13:50.320972 trace git-lfs: filepathfilter: accepting " a/b/c/d..o.command"

Does anyone have any insights on what could be causing this?
On the other hand, if I had 
 
Thanks,
Sarvi
Occam’s Razor Rules
Next: Saravanan Shanmugham (sarvi)
Message 1 of 3 in “"git commit" of single file takes 5 minutes, mounted fileystem/diskimage with 50G GIT repo + 900G of builds articles”
  1. Saravanan Shanmugham (sarvi)Aug 26, 2019
  2. Saravanan Shanmugham (sarvi)Aug 27, 2019
  3. Taylor BlauAug 27, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.