incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <>
Subject [allura:tickets] #6388 Deep trace of single pageload
Date Fri, 20 Dec 2013 18:55:03 GMT

There are a few performance & configuration improvements in this branch, but none of the
particular areas mentioned above are addressed.  Most of the work in this branch is a script
to have a standard benchmark of call counts that can be run for any git revision (can't go
earlier than the creation of the script though).

Run the main script to get current call counts, and to see specific calls `allura/scripts/perf$
./ -v`

Use the shell wrapper to create a CSV file with multiple commits recorded (suitable for graphing
in a spreadsheet app).  E.g.: `allura/scripts/perf$ ./ bdde98d..HEAD

For integration with Jenkins, we should be able to run ` --data-file /some/permanent/location.csv`
and hook that up to


** [tickets:#6388] Deep trace of single pageload**

**Status:** code-review
**Labels:** performance 
**Created:** Mon Jun 24, 2013 04:38 PM UTC by Dave Brondsema
**Last Updated:** Mon Dec 16, 2013 11:07 PM UTC
**Owner:** Dave Brondsema

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 because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message