Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Managing Memory for WebSvn #128

Open
k10blogger opened this issue Oct 8, 2020 · 1 comment
Open

Managing Memory for WebSvn #128

k10blogger opened this issue Oct 8, 2020 · 1 comment

Comments

@k10blogger
Copy link
Member

So some of the users have come back with the error when they compare between two tags or between revisions.
image
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?

@ams-tschoening
Copy link
Contributor

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.

#122

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants