[p4] Large submit problem with P4V

[Robert Cowham]

I have been asked about this at a few sites. My recommendation is always to
do large submits on the command line. P4v is worse than p4win, but even so,
command line is better.

If this is a regular occurrence then it doesn't take much to put a script
together which can be called from the Tools menu for such situations...

Robert

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Brad Holt
> Sent: 13 May 2006 07:55
> To: Jeff Jensen; Chuck Emary; Jamison, Shawn; 
> perforce-user at perforce.com
> Subject: Re: [p4] Large submit problem with P4V
> 
> I've seen similar behaviour with both P4V and P4Win.  In 
> P4Win, with the last couple of releases, there are events 
> that not only run "p4 opened"
> (like it has done in the past), but also a couple of 
> different fstat calls on all opened files in your pending 
> integration changelists.  I assume this is checking for 
> unresolved files or something.  This gets crippling when one 
> of your users is creating a new 400,000 file branch.
> Having a large pending changelist makes P4Win unusable until 
> the changelist is submitted.  The answer of course is to use 
> the command line client for new branches and submissions, but 
> that's a hard sell around here.
> 
> For some reason these fstat calls seem to lock up a lot of 
> the metadata.
> The phone starts ringing as a nasty submit queue forms up 
> waiting for this fstat sanity checking to finish.  Surprising 
> behaviour I think.
> 
> Anyway, this P4Win problem sounds a bit different from what 
> is being discussed here as it seems these problems are before 
> the actual submit phase while the user has a pending, 
> unsubmitted change.
>