Closed
Bug 755928
Opened 12 years ago
Closed 12 years ago
[research] build list of views that take > 800ms (HTTP GET only)
Categories
(support.mozilla.org :: Code Quality, task, P1)
support.mozilla.org
Code Quality
Tracking
(Not tracked)
RESOLVED
FIXED
2012.10
People
(Reporter: willkg, Assigned: rrosario)
Details
(Whiteboard: u=dev c=general p=1)
This bug is for going through the graphs and building a list of GET views in kitsune that take > 800ms.
Updated•12 years ago
|
Target Milestone: --- → 2012.10
Assignee | ||
Updated•12 years ago
|
Priority: -- → P1
Whiteboard: u=dev c=general p=1
Reporter | ||
Updated•12 years ago
|
Summary: [research] build list of views that take > 800ms → [research] build list of views that take > 800ms (HTTP GET only)
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → rrosario
Assignee | ||
Comment 1•12 years ago
|
||
I did most of this today. I am leaving it open until I file the followup bugs. Below are my notes. Landing pages: stats.timers.sumo.view.landings.views.*.GET.upper_90 : all <50ms KB: stats.timers.sumo.view.wiki.views.*.GET.upper_90 : mostly good. stats.timers.sumo.view.wiki.views.document.GET.upper_90 : <100ms stats.timers.sumo.view.wiki.views.revision.GET.upper_90 : varies between ~500ms and ~1000ms stats.timers.sumo.view.wiki.views.get_helpful_votes_async.GET.upper_90 : all over the place from <1s to almost 25s. It is an ajax call to populate an optional chart and not used much so I don't think it is very low priority if any. stats.timers.sumo.view.wiki.views.review_revision.GET.upper_90 : has some peaks up to 1500ms. This is a page for KB reviewers. I think it is medium to low priority to fix. I am guessing the generating diffs is what slows it down. We could potentially cheat and do that in js on demand. Support Forum: stats.timers.sumo.view.questions.views.*.GET.upper_90 : good except… stats.timers.sumo.view.questions.views.questions.GET.upper_90 : 750ms - 2s. high priority stats.timers.sumo.view.questions.views.edit_answer.GET.upper_90 : 500ms - 3s. low priority Search: stats.timers.sumo.view.search.views.*.GET.upper_90 : good Forums: stats.timers.sumo.view.forums.views.*.GET.upper_90 : good Users (profile page, etc): stats.timers.sumo.view.users.views.*.GET.upper_90 : good Private Messages: stats.timers.sumo.view.messages.views.*.GET.upper_90 : good Groups: stats.timers.sumo.view.groups.views.*.GET.upper_90 : good except stats.timers.sumo.view.groups.views.profile.GET.upper_90 : all over the place up to ~15secs. Probably medium priority to fix. Gallery: stats.timers.sumo.view.gallery.views.*.GET.upper_90 : good Dashboards: stats.timers.sumo.view.dashboards.views.localization.GET.upper_90 : some peaks up to 2secs stats.timers.sumo.view.dashboards.views.contributors.GET.upper_90 : mostly good with some peaks above 1-2secs KBForums: stats.timers.sumo.view.kbforums.views.*.GET.upper_90 : good
Assignee | ||
Comment 2•12 years ago
|
||
Followup bugs have been filed. (In reply to Ricky Rosario [:rrosario, :r1cky] from comment #1) > stats.timers.sumo.view.wiki.views.get_helpful_votes_async.GET.upper_90 : all > over the place from <1s to almost 25s. It is an ajax call to populate an > optional chart and not used much so I don't think it is very low priority if > any. Bug 761314 > stats.timers.sumo.view.wiki.views.review_revision.GET.upper_90 : has some > peaks up to 1500ms. This is a page for KB reviewers. I think it is medium to > low priority to fix. I am guessing the generating diffs is what slows it > down. We could potentially cheat and do that in js on demand. Bug 761316 > stats.timers.sumo.view.questions.views.questions.GET.upper_90 : 750ms - 2s. > high priority Bug 674304 > stats.timers.sumo.view.questions.views.edit_answer.GET.upper_90 : 500ms - > 3s. low priority Bug 761317 > stats.timers.sumo.view.groups.views.profile.GET.upper_90 : all over the > place up to ~15secs. Probably medium priority to fix. Bug 761320
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•