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

Re: how to deal with HUGE repositories?

From: Mike Mason <mgm_at_thoughtworks.net>
Date: 2004-11-16 01:08:30 CET

Subversion Newbie wrote:

>Hi Mike,
>The reason why we need "svn update" to be really fast
>is: after a user "checks in" a modified file, she'll
>want to view it through the website very shortly
>afterwards. If there is a substantial delay (let's
>say more than 4 seconds after commiting the changed
>file) then we'll have complaints. These expectations
>are based on the current way of doing things, where
>users change files on what is basically a live
>website. (Not a pretty sight, huh?)

Aha. Sounds like you need a post-commit hook that goes and updates just
the files they've changed on the "web" machine. Since we know at commit
time what the user has changed, we can do a really fast update.

I'm not 100% up to speed on commit hooks, but there's more info here:

The good thing about a post-commit update hook is that the user's commit
won't actually finish until the update has finished, thus they can go
and "instantly" see the changed file.

You might still want to run a full update on the web area, but could do
that during off-peak hours or something.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 16 01:27:23 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.