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

Re: automatic deployment or websites

From: Ryan Schmidt <subversion-2006q2_at_ryandesign.com>
Date: 2006-05-19 20:35:25 CEST

On May 19, 2006, at 20:17, Jamie wrote:

> My concern with performance is not due to subversion its self. The
> server is currently hosting part of a high traffic website
> streaming audio and video. The owners want to move the remainder of
> the site (all pages) to the same server, I have warned them that I
> don't think this is a good idea as I am not sure if the server will
> cope too well.
> This is why I want to keep subversion stress on the server to a
> minimum. When you perform a subversion update and there have been
> no changes I guess all subversion does it check the version number
> of the repos against the working copy version number? Would this
> not be about the same checking a text file?
> I guess I was thinking it would check all the files for some
> reason. Can someone confirm this?

It will check several (I think) files in each .svn directory in the
server's working copy. There's an .svn directory in each directory in
your working copy, so your update performance will be directly
proportional to the number of directories in the project. On our
internal development server, which handles Subversion working copies,
the repository, Apache, mail, MySQL and lots more, updating a working
copy, regardless of whether it has any changes, can take a very long
time as it has to read all those .svn directories again because
they're not in the disk cache. This can make the other operations on
the server slow to a crawl as they all fight for disk access. It's
even running on an internal RAID 5 array. So, yeah. Not optimal.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 19 20:36:53 2006

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.