{"thread":{"id":"25868","subject":"git-p4: slow doing a commit due to weird perforce behaviour?","startedAt":"2010-11-29T14:39:26Z","lastAt":"2010-11-29T14:39:26Z","messageCount":1,"participants":["Luke Diamand"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"156800","messageId":"1291041566.1990.48.camel@kipper","threadId":"25868","inReplyTo":null,"subject":"git-p4: slow doing a commit due to weird perforce behaviour?","fromName":"Luke Diamand","fromEmail":"luked@broadcom.com","sentAt":"2010-11-29T14:39:26Z","receivedAt":"2010-11-29T14:39:26Z","isPatch":false,"sender":{"key":"luked@broadcom.com","avatar":null},"body":"Am I just imagining this? It's more of a perforce question than a git\nquestion I'm afraid.\n\ngit-p4 seems to be quite slow sometimes at submitting changes. At least\nfor me, it seems to be down to the generation of the diff, which is done\nwith \"p4 diff -du ...\".\n\nIf I do \"p4 diff ...\" or \"p4 diff -dc ...\" then the response comes back\nstraight away, and seems to be based purely on the currently checked out\nfiles.\n\nIf instead, though, I do \"p4 diff -du\" then it appears to do a diff of\nevery file, or something. It's able to spot files that I haven't\nactually checked out, but is *much* slower.\n\nDoes anyone else get this or is it just me?\n\n% time p4 diff -du ...\n\nreal\t0m9.082s\nuser\t0m6.560s\nsys\t0m0.952s\n\n% time p4 diff -dc ...\n... - file(s) not opened on this client.\n\nreal\t0m0.021s\nuser\t0m0.000s\nsys\t0m0.000s\n"}]}