Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Our Subversion server goes to 100% CPU consume after some hours of work. A restart solve the problem for some hours only. The commit and checkout will be very slow in this case.

How can I find the cause of the problem and solve it. Is there a monitor that show the running command and which client has produce it?

share|improve this question

migrated from Aug 3 '12 at 18:28

This question came from our site for professional and enthusiast programmers.

I would start by investigating the svnserve with Process Explorer to see if there is also a lot of disk I/O or if the load is in user space or interrupts or DPCs, then I would use Process Monitor to find out what is really doing. Pay attention that Process Monitor will increase significantly the load on the server.

share|improve this answer
This can helpful if I a developer of svnserve. But I am a user. This information will only show where the CPU is consumed but not why. – Horcrux7 Aug 6 '12 at 15:45
I agree. The result depend on the skill of the one who use those tools. You can use WireShark to record the network traffic. Correlate this with CPU usage and you will find the culprit. – Mircea Vutcovici Aug 6 '12 at 22:50

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.