Johan Corveleyn <johan.corveleyn_at_uz.kuleuven.ac.be> wrote on 05/06/2009
11:16:54 AM:
> Some more info in case anyone is still interested :) ...
>
> Using one of the "ignore-whitespace" options with svn blame (-x-b or
> -x-w) improved the performance a lot (though it's still too slow to
> be really useful in an "online" scenario). I guess that's because
> some large all-lines-changing-indentation-revisions can be filtered out.
>
> For the collapsed history, I get with "svn blame -x-b" (over https):
> - Still ~8 minutes for file1.xml (2 Mb large, 799 revisions)
> - ~2,5 minutes for file2.xml (1,5 Mb, 471 revisions)
>
> I guess file2.xml had some all-lines-changing-indentation-revisions
> in those 471 revisions, that are now effectively filtered out by -x-b.
>
> For the full history, I get with "svn blame -x-b" (over https):
> - ~40 minutes for file1.xml (2 Mb large, 5500 revisions)
> - ~15 minutes for file2.xml (1,5 Mb large, 2300 revisions)
>
> Still interested in any feedback, people with similar
> experiences/numbers, workarounds, ...
>
> Maybe using another diff command on the client (--diff-cmd option),
> one that is really super-fast, would help?? Anyone has any
> suggestions on a highly optimized diff for Windows XP (don't know if
> this would help blame at all...)?
I think someone else mentioned this before, but couldn't you pre-compute
the blame output in a post-commit hook? Then people would just go
to a web page/network location to look at the blame output instead
of running the blame themselves?
Kevin R.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2082823
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-06 19:17:36 CEST