https://bugzilla.wikimedia.org/show_bug.cgi?id=60193
Web browser: ---
Bug ID: 60193
Summary: asset-check.py and other front end performance
instrumentation needs further thought
Product: Wikimedia
Version: wmf-deployment
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: Unprioritized
Component: General/Unknown
Assignee: wikibugs-l@lists.wikimedia.org
Reporter: b...@mzmcbride.com
CC: o...@wikimedia.org
Classification: Unclassified
Mobile Platform: ---
Re:
https://github.com/wikimedia/operations-puppet/blob/production/modules/webperf/files/asset-check.py
This asset-check.py script currently checks a few selected main pages and
aggregates the data into Ganglia graphs, as I understand it. A better approach
is probably needed here given that this aggregation makes diagnosis of issues
more difficult when examining the graphs and attempting to trace what caused a
particular spike.
This script also seems to import itertools needlessly and could use minor
additional comments (why the reload(sys)?).
Generally, front end performance instrumentation needs some love. This will
probably be the subject of future tickets.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
