Subversion for version control

I am working on an application whose main goal would be to provide version control management. My idea is to use SVNKit for file registration and registration. However, working with SVNKit, I realized that I did not have the speed that I was looking for. For example, whenever developers create a ChangeRequest that can include changes in 3-40 files, I have to create a directory structure distributed across 32 folders. This takes about 50 seconds. Another example: after creating a change request, developers can add files to the request. Copying even one file from Trunk to a branch takes about 6-7 seconds. My question is: did anyone have such experience and what did you do to improve performance? Also, is my approach correct?

NOTE. I am using the http protocol and cannot use the svn protocol.

+3
source share
3 answers

Typically, SVNKit is a complete implementation implementation . And yes, it is much slower than native. Therefore, if you are not limited only to Java code, you can try:

  • Use native SVN C API.
  • Use Java SVN bindings

For more information, see: http://svnbook.red-bean.com/en/1.5/svn.developer.usingapi.html box "SVNKit Versus javahl"

Also note ... the protocol has virtually no effect on performance (really).

+1
source

( , ?), SVN .

.

, SVN? ? - ?

0

, :

  • SVN , . , .
  • PerfForce, , .
  • GIT , .
  • Mercurial . - . CR/LF.

.

-2

Source: https://habr.com/ru/post/1741723/


All Articles