[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

<?> Deltify, huh, what is it good for<?> Questions on Deltify and recovery

From: Peter Kahn <pkahn_at_connected.com>
Date: 2004-12-13 16:21:41 CET

I have a repository that needs to go through recovery and am ready to
sit down with a good book and wait 8-16 hours for the process to
complete. I am somewhat unhappy about the length of time that this
process will take and am wondering if there is any regular maintenance
procedure that I could do to make a recovery faster.



Avoiding the need for recovery would be best, but I'm not quite sure how
I got here. For about a month, I have had WebDav and svnserve runnining
on this repository without a problem. My users have been moving to
svnserve as it is much faster than the WebDav access.


This morning I noticed that svnserve was no longer running and read the
dreaded passage from the Red Bean book that states how a crash can wedge
a repository. This seems like the likely cause, but I can't be sure
because I haven't yet found the smoking gun of the crash and could be
blaming an effect for being a cause.



Here is the real question. I have read some posts on other lists about
how running deltify can be a useful maintenance operation. I have found
the description of what deltify does to be a little Spartan for my
tastes and I'm just not sure if it would procude any kind of gain.


If I run deltify on a daily basis, would it make a recovery faster? If
I should be running deltify regularily, should it be run just on HEAD or
should it be run on ALL revisions since the last time deltify was run?


Does anyone have any recommendations on this matter? If so, I hope
you'll share them.





Peter Kahn
Received on Mon Dec 13 16:22:47 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.