[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    [Issue 3907]  svn up should create a server-sided diff and apply it
From:       rhuijben () tigris ! org
Date:       2011-05-30 18:59:44
Message-ID: 20110530185944.AD9BC540101 () sc157-tigr ! sjc ! collab ! net
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=3907



User rhuijben changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|NEW                       |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |INVALID
--------------------------------------------------------------------------------




------- Additional comments from rhuijben@tigris.org Mon May 30 11:59:43 -0700 2011 -------
Please discuss things on the user or development list first before creating
an issue.

This simplistic solution doesn't handle mixed revision working copies and the 
way svn diff is implemented it would use several times more data to handle the 
patch this way.
(svn diff is processed client side and requires access to the old and new 
versions of the file via url, while svn update just transfers a compressed 
binary difference).

Most likely the reason why your update is slow is that some of your files have 
different revisions then other. The update process starts with sending these 
numbers to the server. The server then spools just the binary differences back 
that are needed. (Which is several times more efficient then your suggested 
approach).

(this is then applied to everything that changed in the tree, changes merged, 
etc. etc.)

Finally the update bumps the revision of all paths to the new revision.

In 1.6 walking the old revisions and bumping the new revisions is sometimes 
expensive (and on Windows obtaining a lock for the entire tree). This is much 
more efficient in 1.7 where Subversion switches to a single database in the 
working copy root.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=463&dsMessageId=2753261

To unsubscribe from this discussion, e-mail: [issues-unsubscribe@subversion.tigris.org].
[prev in list] [next in list] [prev in thread] [next in thread]