You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@allura.apache.org by Dave Brondsema <br...@users.sf.net> on 2013/10/21 18:09:10 UTC

[allura:tickets] Ticket 6707 discussion

- **Milestone**: forge-nov-01 --> forge-backlog



---

** [tickets:#6707] Slow commit_browser_data**

**Status:** open
**Labels:** performance 
**Created:** Tue Sep 24, 2013 03:52 PM UTC by Dave Brondsema
**Last Updated:** Fri Oct 04, 2013 07:38 PM 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.