Based on New Relic "xray sessions", potential candidates to investigate more are:
* controllers/root.py `Neighborhood.query.get`: 11% of avg _nav.json request. Time spent is all in mongo. Cache it for a while? * model/project.py `install_anchored_tools`: 15% of avg _nav.json request. Most of tim spent is in mongo. Seems to be the `self.app_configs` property load? * lib/security.py `obj.neighborhood_project`: 7.3% of avg _nav.json request. Cache it for a while? * post_thread/post_widget.html has repeated sequential calls to `Artifact.refs` taking 13% of avg ticket view, backrefs (5.2%), user icon_url which is already memozied (8.4%) --- ** [tickets:#6388] Deep trace of single pageload** **Status:** open **Labels:** performance **Created:** Mon Jun 24, 2013 04:38 PM UTC by Dave Brondsema **Last Updated:** Tue Dec 03, 2013 06:05 PM UTC **Owner:** nobody Let's do a trace (e.g. start with TimerMiddleware verbose mode to get every pymongo call; maybe try `line_profiler` later) of common functionality to every page. Focus on just the core parts of allura, not looking into the specifics of whatever page you're on. Might be helpful to test hitting an external link URL, so there's not much tool-specific going on, just core route handling, project/tool lookup, permission checks, etc. Identify opportunities for improvement. --- 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.
