Forum Discussion

ekiza23's avatar
ekiza23
Contributor
13 years ago

Extremely slow synchronization with SubVersion Source Control

I have intregrated TestComplete 9 EE with Subversion (http://community.smartbear.com/forum/post/?mode=singleThread&thread=f74017e8-1419-4923-bd05-9e3f108070be).



I opened a project suite, and added the project suite and the project to the Source Control. I checked in and all the items were with the padlock icon which means that they're under version control.



In the options menu, 

Check out on open (Unchecked)

Check in on close (Unchecked)

Bind new items to SCC automatically (Unchecked)

Show provider messages (Checked)



SCC Provider: SmartBear SVN plug-in for TestComplete 9

Properties:

Use the current Windows user name as the default login name (Checked)

Use cached authentication information (Unchecked)

Use locks for checked -out files (Unchecked)



When I open the project suite that I added to the repository, it shows the progress bar for a few seconds and then moves to the

Opening the project suite. Please wait... 

message



And it seems to get stuck there until I get a message saying that the application is not responding. 



Some 5 minutes later... the project opens.



Also, I noticed that when I did the commit, the app took an unusual ammount of time for less than 4 MB...



Is this the normal behavior? If so, it is extremely slow, down to the point where I am tempted to go back to manually committing the file changes into the repo with a regular SVN client (say Tortoise).


  • anik_cadieux's avatar
    anik_cadieux
    Contributor
    12 years ago
    Hello,



    I have the same problem and I the only solution I found is to go back to manually committing the file changes into the repo with a regular SVN client (say Tortoise).



    Progress bar appears very ofter and it takes a much longer time to commit changes than with Tortoise (about 4 times longer).



    I am currently investigating the problem so any help or tip would be appreciated.



    Thank you !
  • Julia_K's avatar
    Julia_K
    SmartBear Alumni (Retired)
    13 years ago
    Hello Christian,

    You may be facing a known problem.

    Are you using an https repository?

    Can such slowness be observed only when you are working with a particular TestComplete project? Does that project contain many items and folders?

    Could you please check how long it takes to perform the same operations with your project via any other SVN client?

    Thank you.

  • ekiza23's avatar
    ekiza23
    Contributor
    12 years ago
    Updating manually with Tortoise SVN was a matter of a few seconds. TestComplete was EXTREMELY slow to update and I opted to do all the commits manually outside of TestComplete. 



    Very inconvenient, I think that Anik has had the same issue and did exactly what I did at the time (TestComplete 9.0). 



    Since I had no news on that I haven't even bothered to try it with 9.1 nor 9.2. The first experience was too troublesome and the manual commit, although not a full integration, has worked nice enough so far. 



    If I had reply from SmartBear on some specific problems identified and fixed on this subject that improve significantly the performance, I may consider try it again as it may be very useful...
  • ztilleto_1's avatar
    ztilleto_1
    Contributor
    12 years ago
    Same issue here... TC 9.2



    When I check a box from the Visual view of the project it takes minutes to accept the change before I can access TC again..



    Gonna try and remove SVN from the project and make manual commits instead. Had hoped for this to work better now, as it would help..
  • TanyaYatskovska's avatar
    TanyaYatskovska
    SmartBear Alumni (Retired)
    12 years ago

    Hi Guys,


     


    There is a known issue in TestComplete 9.20 - if a project is bound to SCC, the editing/working process becomes very slow. This issue was fixed in TestComplete 9.30 that is going to be released very soon. If the issue is critical for you, refer to the TestComplete Support team - they have a patch that solves it.