git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luke Diamand" <luked@broadcom.com>
To: git@vger.kernel.org
Subject: git-p4: slow doing a commit due to weird perforce behaviour?
Date: Mon, 29 Nov 2010 14:39:26 +0000	[thread overview]
Message-ID: <1291041566.1990.48.camel@kipper> (raw)

Am I just imagining this? It's more of a perforce question than a git
question I'm afraid.

git-p4 seems to be quite slow sometimes at submitting changes. At least
for me, it seems to be down to the generation of the diff, which is done
with "p4 diff -du ...".

If I do "p4 diff ..." or "p4 diff -dc ..." then the response comes back
straight away, and seems to be based purely on the currently checked out
files.

If instead, though, I do "p4 diff -du" then it appears to do a diff of
every file, or something. It's able to spot files that I haven't
actually checked out, but is *much* slower.

Does anyone else get this or is it just me?

% time p4 diff -du ...

real	0m9.082s
user	0m6.560s
sys	0m0.952s

% time p4 diff -dc ...
... - file(s) not opened on this client.

real	0m0.021s
user	0m0.000s
sys	0m0.000s

                 reply	other threads:[~2010-11-29 14:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1291041566.1990.48.camel@kipper \
    --to=luked@broadcom.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).