I found your open ticket, and I’ll add some notes for the team that handles high disk usage. There is no practical way to setup DreamObjects to run your subversion on that I’m aware of. For it to be hosted on your shared webserver, the files would need to be local. I’ll see what I can do about getting that decision reversed.
What can help though, and it would require starting the repo over from scratch, is to keep static binary files and large files that don’t change or need to be in revision control outside of svn, and keep them in DreamObjects instead. This way the svn repo will just contain data that needs to change like source code, and all static resources can be in DreamObjects or elsewhere. Another good reason to do this is that svn keeps a revision history of all those binary and large files too, when perhaps that info isn’t needed.
We’ll get back to you via the support ticket with more details.