# Fast Subversion Update on a Rarely Updated Large Third Party Repository

I have a project with a large thirdparty repository, which contains tons of sources and binaries, which are seldom updated. While subversion might not be the best suited tool for the job, the size of that repository is not insane enough to consider using something else… yet!

The problem with that rarely updated large repository is that performing an svn update on it can take quite a while even though there are no updates to perform. The reason is that subversion checks that no files are missing on the local checkout directory, because you can perform non recursive partial checkouts or updates, or potentially alter the whole structure after a checkout.

Nevertheless, if all you do is mirror the subversion directory content on your drive, you may have a faster option than svn update. You can use svn info to compare the local revision of your checkout to the latest available version on the server. If the revisions match it means your repository is up to date and you can avoid the costly svn update.

I regularly use a powershell script to automate that process.

Powershell script