Re: SVN 1.7/1.8 commit after delete performance issue

has a better user experience. When multiple paths are passed they are usually all in the same (wc and) file system. Bert From: Philip Martin Sent: 30/07/2013 14:53 To: Bert Huijben Cc: Alexander Lüders; dev@subversion.apache.org Subject: Re: SVN 1.7/1.8 commit after delete performance issue Bert

Re: SVN 1.7/1.8 commit after delete performance issue

Alexander Lüders a...@entimo.de writes: How to proceed now? Shall I file a bug report? It's already fixed on trunk and I've just proposed it for 1.8. -- Philip Martin | Subversion Committer WANdisco | Non-Stop Data

Re: SVN 1.7/1.8 commit after delete performance issue

That's great. Thank you very much. Am 09.08.2013 12:26, schrieb Philip Martin: Alexander Lüders a...@entimo.de writes: How to proceed now? Shall I file a bug report? It's already fixed on trunk and I've just proposed it for 1.8.

Re: SVN 1.7/1.8 commit after delete performance issue

Hi Philip, thanks for the response. Passing the deleted file means that the path based optimisations are not available in 1.7/1.8 and so svn_io_sleep_for_timestamps sleeps for longer. That sounds like a fair assumption to me. Do you see any oportunity to implement some kind of optimization

Re: SVN 1.7/1.8 commit after delete performance issue

Alexander Lüders a...@entimo.de writes: Hi Philip, thanks for the response. Passing the deleted file means that the path based optimisations are not available in 1.7/1.8 and so svn_io_sleep_for_timestamps sleeps for longer. That sounds like a fair assumption to me. Do you see any

RE: SVN 1.7/1.8 commit after delete performance issue

Subject: Re: SVN 1.7/1.8 commit after delete performance issue Alexander Lüders a...@entimo.de writes: Hi Philip, thanks for the response. Passing the deleted file means that the path based optimisations are not available in 1.7/1.8 and so svn_io_sleep_for_timestamps sleeps for longer

Re: SVN 1.7/1.8 commit after delete performance issue

Bert Huijben b...@qqmail.nl writes: Just pick the parent of the first delete or something like that. The path should be a valid path on the same file system, nothing special. It is just used for guessing the timestamp granularity. I suppose that might work for commit, but it's not clear how

Re: SVN 1.7/1.8 commit after delete performance issue

Philip Martin philip.mar...@wandisco.com writes: Index: subversion/libsvn_client/commit.c === --- subversion/libsvn_client/commit.c (revision 1508338) +++ subversion/libsvn_client/commit.c (working copy) @@ -1027,8 +1027,14 @@

RE: SVN 1.7/1.8 commit after delete performance issue

@subversion.apache.org Subject: Re: SVN 1.7/1.8 commit after delete performance issue Bert Huijben b...@qqmail.nl writes: Just pick the parent of the first delete or something like that. The path should be a valid path on the same file system, nothing special. It is just used for guessing the timestamp

SVN 1.7/1.8 commit after delete performance issue

Dear Subversion Team, thank you for your effort in developing and constantly improving Subversion. We currently use Subversion 1.6.x for our application and are evaluating the migration to 1.7 and 1.8. While running our tests I have discovered a possible performance problem in the 1.7/1.8

Re: SVN 1.7/1.8 commit after delete performance issue

Alexander Lüders a...@entimo.de writes: 1) svnadmin create testrepo 2) svnserve --listen-host=localhost --listen-port= --root=testrepo 3) svn co svn://localhost:/ wc 4) create file testXXX.html in wc 5) svn add wc/testXXX.html 6) svn commit wc/testXXX.html 7) svn delete

Re: SVN 1.7/1.8 commit after delete performance issue (this time with previously missing attachment)

On Mon, Jul 29, 2013 at 6:34 AM, Alexander Lüders a...@entimo.de wrote: How to reproduce: I assembled a little Java program that executes all steps above and can be configured via command line. For each step it spawns a separate process, which executes the corresponding task. This was done