History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-2218
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Maikel vd Hurk
Votes: 5
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
QuickBuild

Perforce add capability to do parallel sync

Created: 28/Oct/14 10:20 PM   Updated: 13/Jan/17 02:02 PM
Component/s: None
Affects Version/s: 5.1.36
Fix Version/s: 7.0.0

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
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

 All   Comments   Work Log   Change History      Sort Order:
Maikel vd Hurk [08/Jun/16 10:52 AM]
Any change to add and option to enabled --parallel for perforce syncs?

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.

Gouss [01/Aug/16 02:30 PM]
Hello Robin,

it would be very appreciated if it could done.


regards,
Gouss

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!

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).