Totally agree, the browwe commits is completely useless for us because its performance makes it unusable.. a real show stopper to get a view of commit history as there is no other useful view like this one (since you took aay using trace for this in allura)
--- ** [tickets:#6707] Slow commit_browser_data** **Status:** open **Labels:** performance **Created:** Tue Sep 24, 2013 03:52 PM UTC by Dave Brondsema **Last Updated:** Thu Nov 07, 2013 01:57 AM UTC **Owner:** nobody Sometimes `RepoRootController.commit_browser_data` is pretty slow. Based on log statements, it looks like the slowness is in the first 2 lines of the method. This is supported by timermiddleware instrumentation which has high timings for `svn_lib.log` and `git_tool._iter_commits_with_refs.next` and `git_tool.log.next` We could consider a max time limit similar to [#6695] --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
