Did you try it? The first paramater to `Timer` is a name so that can be whatever. The 2nd and 3rd parameters specify what object/method(s) to time. For the sidebar, the `def sidebar_menu` method exists on every tool, which is why its looping to get them all. But for navbar I think it can be simpler like the other timers. You will have to explore the codebase to find the right top project nav method, and then make the Timer measure that method.
--- ** [tickets:#7977] Improvements to AlluraTimerMiddleware** **Status:** open **Milestone:** unreleased **Labels:** bitesize **Created:** Tue Aug 25, 2015 09:30 PM UTC by Dave Brondsema **Last Updated:** Thu Feb 07, 2019 09:13 AM UTC **Owner:** nobody It'd be useful to have AlluraTimerMiddleware wrap the project nav logic. This would help identify any issues related to that (e.g. project with tons of tools) And the first "ming" timer should be renamed "ming-iter" so that the high call counts it produces is separate from the regular ming counts. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
