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

git-p4: slow doing a commit due to weird perforce behaviour?

From
LDLuke Diamand <luked@broadcom.com>
Date
Nov 29, 2010, 14:39 UTC
Message-ID
<1291041566.1990.48.camel@kipper>

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

Message 1 of 1 in “git-p4: slow doing a commit due to weird perforce behaviour?”
  1. Luke DiamandNov 29, 2010

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.