Jump to content


reconcile for huge folders

reconcile p4v p4

  • Please log in to reply
4 replies to this topic

#1 amolode

amolode

    Advanced Member

  • Members
  • PipPipPip
  • 41 posts

Posted 16 August 2015 - 12:06 PM

Hi,
We use 'reconcile' feature for importing and upgrading 3rd party software code in our Perforce depot.  Usually, 3rd party code is versioned in a separate branch. After the initial import, the code is integrated into a development branch where very minor but still important changes are made. Once a new version of the 3rd party code comes from its vendor we create a new clean client workspace, sync it with the 3rd party from our initial Perforce branch, remove the files with Linux command line 'rm -r' command and transfer the new 3rd party version into the synced but empty workspace. After that we run 'reconcile' either in P4V or with p4 command line.
The problem is that for large folders this command takes a very great amount of time, sometimes a few days. Is there any way to optimize the process, streamline it? Are there any environment variables values, Perforce configurables or other tricks to allocate more RAM to the process in order to speed it up?

#2 P4Sam

P4Sam

    Advanced Member

  • Members
  • PipPipPip
  • 484 posts
  • LocationSan Francisco, CA

Posted 16 August 2015 - 02:50 PM

1) Which version of the server/client are you using?  ("p4 info", "p4 -V")
2) Which part of the reconcile process seems to be taking the bulk of the time?  I.e. if you run:

	time p4 reconcile -a
	time p4 reconcile -d
	time p4 reconcile -e

which phase is the one taking the longest?

#3 amolode

amolode

    Advanced Member

  • Members
  • PipPipPip
  • 41 posts

Posted 17 August 2015 - 02:00 PM

1) client:
p4 -V
Perforce - The Fast Software Configuration Management System.
Copyright 1995-2014 Perforce Software.  All rights reserved.
This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit (http://www.openssl.org/)
See 'p4 help legal' for full OpenSSL license information
Version of OpenSSL Libraries: OpenSSL 1.0.1g 7 Apr 2014
Rev. P4/SOLARIS10SPARC64/2013.3/822226 (2014/04/08).

server:
p4 -V
Perforce - The Fast Software Configuration Management System.
Copyright 1995-2014 Perforce Software.  All rights reserved.
This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit (http://www.openssl.org/)
See 'p4 help legal' for full OpenSSL license information
Version of OpenSSL Libraries: OpenSSL 1.0.1g 7 Apr 2014
Rev. P4/SOLARIS10X86_64/2013.3/822226 (2014/04/08).


2) All our previous runs of reconcile were without optional parameters.

#4 P4Sam

P4Sam

    Advanced Member

  • Members
  • PipPipPip
  • 484 posts
  • LocationSan Francisco, CA

Posted 17 August 2015 - 02:13 PM

Run "p4 info" to get the server version -- "p4" is the client, "p4d" is the server, and running "p4 info" tells p4 to ask p4d for its version info.

The next time you run a reconcile, try running the three steps separately as described (-a, -d, -e) and see how long each takes.  That might give us a better idea what "tricks" to apply to speed it up.

#5 amolode

amolode

    Advanced Member

  • Members
  • PipPipPip
  • 41 posts

Posted 18 August 2015 - 11:25 AM

p4 info:
User name: perforce
Client name: jira
Client host: jira
Client unknown.
Current directory: /user/local/perforce/server
Peer address: 147.234.154.121:55705
Client address: 147.234.154.121
Server address: jira.ecitele.com:1666
Server root: /user/local/perforce/server
Server date: 2015/08/18 14:24:40 +0300 IDT
Server uptime: 2571:48:45
Server version: P4D/SOLARIS10X86_64/2013.3/876375 (2014/06/10)
Authorization server: jira:1999
Server license: jira:1999
Case Handling: sensitive





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users