| << Back to previous view |
|
[QB-2218] Perforce add capability to do parallel sync
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 5.1.36 |
| Fix Version/s: | 7.0.0 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Maikel vd Hurk | Assigned To: | Unassigned |
| Resolution: | Fixed | Votes: | 5 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
Perforce add capability to do parallel sync, see:
--parallel Specify options for parallel file transfer. The configuration variable net.parallel.max must be set to a value greater than 1 to enable the --parallel option. threads=n sends files concurrently using n independent network connections. The specified threads grab work in batches. batch=n specifies the number of files in a batch. batchsize=n specifies the number of bytes in a batch. min=n specifies the minimum number of files in a parallel sync. A sync that is too small will not initiate parallel file transfers. minsize=n specifies the minimum number of bytes in a parallel sync. A sync that is too small will not initiate parallel file transfers. More info: http://www.perforce.com/perforce/doc.current/manuals/cmdref/p4_sync.html#p4_sync.usage.parallel |
| Comments |
| Comment by Maikel vd Hurk [ 08/Jun/16 10:52 AM ] |
| Any change to add and option to enabled --parallel for perforce syncs? |
| Comment by Robin Shen [ 09/Jun/16 12:10 AM ] |
| We'd like to get more votes on this before adding this as it may impact current Perforce checkout significantly if there are many builds doing checkouts. |
| Comment by Gouss [ 01/Aug/16 02:30 PM ] |
|
Hello Robin,
it would be very appreciated if it could done. regards, Gouss |
| Comment by Gouss [ 08/Aug/16 12:36 PM ] |
|
Robin, I suppose this could be some advanced configuration, disabled by default, with a warning in the comment. Notice this also has to be authorized on the server to be really effective.
Using groovy and commandline class we are gaining more than 33% (usually just under 50%) on our 7 hours night sync ... (but it does not manage the perforce client for us as QB does :)) We do not want to locally fork from the source but on the other hand the gain is tremendous! |
| Comment by Robin Shen [ 09/Aug/16 12:27 AM ] |
| We will check into this in next big QB release (assumed to be available at end of this year). |