Merge lp:~lifeless/launchpad/foundations into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | Stuart Bishop on 2010-08-19 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 11396 |
| Proposed branch: | lp:~lifeless/launchpad/foundations |
| Merge into: | lp:launchpad |
| Diff against target: |
440 lines (+158/-73) 2 files modified
lib/lp/scripts/utilities/pageperformancereport.py (+154/-68) utilities/page-performance-report-daily.sh (+4/-5) |
| To merge this branch: | bzr merge lp:~lifeless/launchpad/foundations |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Stuart Bishop | 2010-08-11 | Approve on 2010-08-12 | |
|
Review via email:
|
|||
Commit Message
Page performance report improvements - top N urls and 99th percentile
Description of the Change
Generate a page performance report page that will (hopefully) be a useful hit-list for developers to focus on.
| Stuart Bishop (stub) wrote : | # |
| Robert Collins (lifeless) wrote : | # |
Thanks Stuart; the width of 10 for the candidates-timeout graphs is a
little weird; I think it should take the same upper bound - or even a
higher one of the max time in the dataset.
-Rob
| Robert Collins (lifeless) wrote : | # |
Oh, and I was a muppet, setting the timeout -2 *default* to 10, should
have set it to 12, the staging timeout which would cut off
appropriately at 10. Mea culpa.
| Robert Collins (lifeless) wrote : | # |
Stuart, I've updated this with a patch to raise the default timeout to
12 (stagings current timeout) and to separate out the
graph capping (50% above timeout : we regularly go up to this or
higher due to the way the timeouts work), and the stddeviation
calculations : our numeric stats were being distorted by the
calculations to make the histograms nice.
Thanks,
Rob

I've fixed some bugs in this - it doesn't look like it had been tested.
I've merged it in with changes I had neglected to push in the days before the Epic but have been running live. This work is in lp:~stub/launchpad/page-performance-report. It seems to be working locally just fine with a single log downloaded from devpad. I've pushed this to the tree on devpad so we can see the result with the scheduled run.