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

slow "stg push" on NFS

From
CLChuck Lever <cel@citi.umich.edu>
Date
Sep 19, 2005, 19:01 UTC
Message-ID
<432F0AFA.3050401@citi.umich.edu>
hi catalin-
still looking at this problem.

thanks to the several recent patches that add fast-forward support, CPU utilization seems to no longer be a problem in general. what appears to be happening is that each push operation deletes and recreates everything in the working directory.

for shared file systems, creating and deleting files will always be synchronous. anything we can do to eliminate the need for deleting and recreating files that are not changed by a commit would be great.

(i've also noticed that an "stg pop / stg push" sequence causes 'make' to rebuild everything -- possibly due to the same reason?)

am i all wet here?

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

Next: Catalin Marinas
Message 1 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.