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

Re: differences in speed between svn:// and file:///

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-09-05 21:25:14 CEST

Pieter wrote:
> Hi,
>
> Whils using version 1.2, I regularry noticed differences in speed between
> the file:///-way and the svn://-way: the file:/// took sometimes minutes in
> stead of seconds for during a commit or update.
>
> Is this problem yet solved in one of the versions that came later? In the
> upcoming 1.4-release? Anybody knwos anything about this problem?

Of course: A file:/// commit must be slower than a svn:// commit. If you
think about it you will know why:
the bottleneck is the harddrive. During a commit, the client first has
to diff the whole working copy. Then send that diff to the server. The
server has to receive the diff, and apply that diff to the repository.
All this requires a *lot* of disk access.
With file:/// access, the disk access of the server part is on the same
machine or even the same drive as the client, so the harddrive gets
stressed more. If you however commit via svn://, then the repository
part of the harddrive access happens on a different server.

Even if you have the svnserve running on the same machine where you also
tried the file:/// access: svnserve is a different process. That way the
OS can optimize the two processes with their disk access.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Sep 5 21:27:34 2006

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

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