Jump to content

Unity 4.2 and Perforce

Unity Perforce Slow

  • Please log in to reply
1 reply to this topic

#1 djindepth



  • Members
  • Pip
  • 1 posts

Posted 14 August 2013 - 03:03 PM

My team has just upgraded to Unity 4.2 which supports Perforce as a version control platform. We are experiencing slow connect times, slow transfers, freezes and incomplete submissions using this system thus far. We have followed this document as much as we could and have yet found any supporting documents from Perforce. Any advice would be appreciated.


#2 P4Sam


    Advanced Member

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

Posted 14 August 2013 - 09:33 PM

Are you only seeing these problems when using the Unity interface to Perforce, or do you have the same problems when using other Perforce client apps (e.g. P4V or the P4  command line)?

What exactly does one of the "incomplete submissions" look like?  Perforce is supposed to enforce atomic submits; if there's a problem transferring any of the files during a submit, none of them are committed.  After an incomplete submission, are some of the files in the changelist left open and some submitted, or do some of the files disappear, or is this only an issue with "submissions" consisting of multiple changelists that are being batched together by some sort of automation (i.e. some changelists are submitted but some are not)?

Is this with a local network, or over a WAN connection?  How many people are using the system concurrently, and roughly what sort of hardware is the Perforce server on?

Also tagged with one or more of these keywords: Unity, Perforce, Slow

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users