Managing Memory for WebSvn

Open k10blogger opened this issue 5 years ago • 1 comments

So some of the users have come back with the error when they compare between two tags or between revisions. Pushing the PHP to 1GB memory has solved the issue for now.

But i am wondering is there something that can be done to optimize this. Is there anyway this can be improved?

Oct 08 '20 18:10 k10blogger

Please link the concretely mentioned code lines in the version of WebSVN you are using. Besides that, the only thing I can suggest right now is to simply output the data available at those lines and have a look if it makes sense that that much data is available. Sometimes this is simply how things work, though multiple hundreds of MiB really look a bit unusual.

Would be interesting to know if it's XML-result coming from SVN or something like that. Additionally try to output the commands sent to SVN to generate that large output, if it's coming from SVN at all.

I wonder if this has to do with the recent changes to always render all contents of a repo recursively? You might try disabling that to see what happens.

https://github.com/websvnphp/websvn/pull/122

Oct 09 '20 07:10 ams-tschoening