Hello Cesar, Sorry for the delay. Could you check you JNA version on the old and the new machine? If I remember correctly, upgrade to newer JNA caused problems for some users, but downgrade helped. If JNA version is the same, do you have a possibility to profile SVNKit to find what causes performance problems?
Since 1.7 Subversion has new working copy format, based on SQLite database, so all algorithms were completely changed, but the most of the users are happy with SVNKit 1.7, so I'm sure all performance problems are solvable. -- Dmitry Pavlenko, TMate Software, http://subgit.com/ - git-svn bridge > Hi, > > We use the svnkit/jsvn on AIX and I'm migrating our development/source code > to new server. > I get into a issue with "jsvn status" and "jsvn update" performance.... > just make it unsable... > > The SVN server/apache/webdav run over other machine.... > > The old server (workdir): AIX 5.3 , Java 1.6.0 , svnkit version 1.3.2 > (r6267) > The new server (workdir): AIX 6.1 , Java 1.6.0 , svnkit version 1.7.9 > (r9659_v20130411_2103) > > > After checkout our sources on the new server (jsvn 1.7.9) when I execute a > simple "jsvn status" into the main tree (+-24k files/directores total) took > 6 minutes to show the result. > > At the old server, only 11 seconds. > And with jsvn 1.3 on the new server, after checkout again, the "jsvn > status" took 6 seconds... > > Have something to do? or check? Java version? > downgrade to svnkit 1.6 can solve this? (I see lot of others users complain > about svnkit 1.7 performance...) > > Is there some hope to svnkit 1.7 version back have good performance? > > Regards > Cesar
