Anonymous user
Performance analysis: Difference between revisions
no edit summary
(Created page with '= Goals = Page loads on the OpenHatch website should: * '''Be good to clients''': Be processed in less than 0.2 seconds so that users feel the site is snappy. * '''Be good to t…') |
imported>Paulproteus No edit summary |
||
| (3 intermediate revisions by 2 users not shown) | |||
Line 1:
{{Hacking OpenHatch}}
= Goals =
Line 12 ⟶ 13:
= Tools =
==
=== vhost_effort ===
Asheesh wrote an Apache patch and reporting tool called vhost_effort. This patch modifies access.log files in the following way:
Line 24 ⟶ 27:
If "musecs" is prefixed by a plus sign, it means that the musecs actually measured the full time the request took to get to the client. This means we end up including bandwidth time, which skews the figures.
=== Reporting based on vhost_effort ===
If you run these commands on a shell:
Line 37 ⟶ 40:
* hitcount, an unsorted table where column 1 is the number of hits to that URL
* bytes, an unsorted table where column 1 is the number of bytes sent out for this URL
== Client side ==
=== runprofileserver ===
On a development machine, instead of doing:
* ./bin/mysite runserver
you can do
* ./bin/mysite runprofileserver --kcachegrind --prof-path=/tmp/
Now each page load has a .prof file in /tmp/.
Open that up in kcachegrind and you'll see a table of functions. Play around.
| |||