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

Is there any performance difference between subversion checkouts and exports when running your webapplication?

We already implemented this in our deployment process, without measuring for differences (which feels bad. and is bad.).

Our intentions were:
a) dumping overhead (.svn folders and its contents) and
b) improving any directory traversing stuff

Do you have any experience with or measurements for this?

share|improve this question
up vote 3 down vote accepted

It'd be heavily application dependent. With applications I've deployed, it's been irrelevant, as there's absolutely no directory traversal of the application directory going on from within the applications. Some frameworks, particularly Rails, will do auto loading of files within the application and do directory traversal to discover those files, but typical Dir['**/**'] type affairs skip any "hidden" directories such as .svn and .git.

If, for some reason, your application or framework had need to traverse all files under the application folder and didn't ignore hidden directories, there might be some negligible effect, but it would be so application and situation specific that you'll struggle to seek much advice from a generalized answer.

All that said, if you have no reason to push changes back from deployment to the SVN server and you're using a multi directory rolling style deployment mechanism (that is, you export/check out to a new directory every time then update a symlink or similar) you might as well go over to using export. If you just svn update within a deployment directory each time, you might want to stick with it for efficiency's sake..

share|improve this answer

There is less IO for the Subversion client to write an export than a checkout, as the checkout does do a significant amount of locking and loggy writes.

Given that though, I find that having a checkout instead of an export in a web server document root is much better because you can simply 'svn update' to the latest version or run 'svn update -r PREV' to back out a bad push. So I find the convenience of this outweighs any advantage of less IO. This assumes that you are not exporting and then FTP'ing the export to your web server.

How are you deploying to your web server?

share|improve this answer
We have one server onsite where we manage deployment. Yes, there is only one script to roll out a full deployment :). Since we have multiple webservers, the deployment machine updates a checkout to the chosen revision, exports this to another folder, which will then get rsynced to the webservers. – Karsten May 30 '09 at 9:13

One thing that really makes a difference with SVN (especially checkin) is virus scanning. If you can turn AV off for the .svn directories then you'll see a difference.

share|improve this answer

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.