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

Re: slow "stg push" on NFS

From
CLChuck Lever <cel@citi.umich.edu>
Date
Sep 20, 2005, 17:56 UTC
Message-ID
<43304D35.3030601@citi.umich.edu>
In-Reply-To
<1127201053.7019.13.camel@localhost.localdomain>
Catalin Marinas wrote:
Show 13 quoted lines
> On Mon, 2005-09-19 at 15:01 -0400, Chuck Lever wrote:
>>what appears to 
>>be happening is that each push operation deletes and recreates 
>>everything in the working directory.
> 
> 
> The push operation only does a 'git-read-tree -u -m' which updates the
> filesystem. I haven't looked at the git-read-tree code but I suspect it
> only updates the files modified as a result of the merge operation. As
> Blaisorblade reported, if there are big changes between the new HEAD and
> the old bottom of the patch, like file removals and additions, it will
> indeed take more time since git-read-tree cannot deal with them and
> gitmergeonefile.py will be invoked for each file.

ja, indeed, gitmergeonefile.py is doing some heavy lifting in my case. however, i think the bogosity stems from something my new cache API is doing. i can't reproduce this behavior with stock GIT.

begin:vcard fn:Chuck Lever n:Lever;Charles org:Network Appliance, Incorporated;Linux NFS Client Development adr:535 West William Street, Suite 3100;;Center for Information Technology Integration;Ann Arbor;MI;48103-4943;USA email;internet:cel@citi.umich.edu title:Member of Technical Staff tel;work:+1 734 763 4415 tel;fax:+1 734 763 4434 tel;home:+1 734 668 1089 x-mozilla-html:FALSE url:http://www.monkey.org/~cel/ version:2.1 end:vcard

Previous: Catalin Marinas
Message 3 of 3 in “slow "stg push" on NFS”
  1. Chuck LeverSep 19, 2005
  2. Catalin MarinasSep 20, 2005
  3. Chuck LeverSep 20, 2005

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.