|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Could you take several thread dumps while the checkout is happening (kill -3 $PID, or jstack $PID)? This would help with debugging and understanding where some slow points are happening, and any places in the code threads are stuck at.
While doing initial testing before I released I was able to perform checkouts (svn 1.8) with speeds with little (to sometime no) difference than through command line. I will look into setting up an environment to perform svn checkouts with several GB.
Pablob P I have tried to make several attempts at using a native api (javahl, svnkit + native libraries, etc.), however I do not believe they are safe to use. Debugging issues increases the complexity because each native library has a different libsvn implementation (default *nix libsvn libraries, vendor libsvn implementations, etc). SVNKIT offers a pure java implementation which is easier to debug. Another issue is we would need to be careful and make sure to guard against native code potentially crashing the JVM. We could try something similar to what the git plugin does (define the svn executable or pick svnkit), but that would require a major rework.
Pablob P I understand your frustration, but please do not use bad language. I am really sorry about the issue you are experiencing, and I am making efforts to resolve any performance issues users are experiencing.