Feb 26
We have been using SVN for the last few months, now having been CVS users for about 3 years before that. While SVN is a sensible choice for the future, we are finding a few weaknesses in the current implementation and I will be posting details of these over the next few days.
The first issue is that running apache webdav on windows server 2003 we find that it slowly consumes more and more memory until it runs very slowly and eventually stops other processes running correctly.
We have reduced the thread limit in the hope that it will force apache to create a new process once this limit is reached but it does not seem to do that.
We continue the search for a good solution to this...
The first issue is that running apache webdav on windows server 2003 we find that it slowly consumes more and more memory until it runs very slowly and eventually stops other processes running correctly.
We have reduced the thread limit in the hope that it will force apache to create a new process once this limit is reached but it does not seem to do that.
We continue the search for a good solution to this...
Mar 18, 2008 at 5:04 PM I suspect the culprit is Windows (likely the Windows Apache binaries), not SVN itself. I've only run Apache on Windows occasionally, and not very recently, but there seemed to be some slight weirdnesses that weren't present running Apache on Linux. I'd definitely check the Apache site for any Windows tips and tricks.
Mar 19, 2008 at 12:12 AM agreed
best solution is to NOT use windows
i use it as sparingly as possible. it's simply not reliable. and anyone that tells you otherwise is selling something.
if anything, it's good for desktops. IMO using it for anything remotely near a critical server is asking for a world of pain.
Dec 18, 2008 at 9:52 PM best solution, run it on linux where it belongs :)
using svn + apache on linux for years no sign of memory leaks