From: Chuck Lever <cel@citi.umich.edu>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: slow "stg push" on NFS
Date: Mon, 19 Sep 2005 15:01:14 -0400 [thread overview]
Message-ID: <432F0AFA.3050401@citi.umich.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
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?
[-- Attachment #2: cel.vcf --]
[-- Type: text/x-vcard, Size: 439 bytes --]
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 reply other threads:[~2005-09-19 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 19:01 Chuck Lever [this message]
2005-09-20 7:24 ` slow "stg push" on NFS Catalin Marinas
2005-09-20 17:56 ` Chuck Lever
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=432F0AFA.3050401@citi.umich.edu \
--to=cel@citi.umich.edu \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).