Closed Bug 539021 Opened 16 years ago Closed 7 years ago

Implement a system to profile awesomebar loading time

Categories

(Firefox for Android Graveyard :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: vingtetun, Unassigned)

References

Details

I've a dirty patch for that. I need to update it to work on the current fennecmark
would we need a pre loaded profile for this? I would assume a 500 bookmark, 2000 website history would be good enough for this. Would we just measure the time from urlbar tap to awesomebar display? Also could we detect keystroke performance in the url bar during the load? for example: 1) tap url bar 2) start type www.mozilla.org without waiting for awesomebar to load 3) measure the time it takes for www.mozilla.org to be displayed in the url bar 4) measure the time it takes to match an entry
(In reply to comment #1) > would we need a pre loaded profile for this? I would assume a 500 bookmark, > 2000 website history would be good enough for this. Would we just measure the > time from urlbar tap to awesomebar display? Obviously, we need a pre-loaded profile. Do you know where we can find any pre-ready profile? > > Also could we detect keystroke performance in the url bar during the load? for > example: > > 1) tap url bar > 2) start type www.mozilla.org without waiting for awesomebar to load > 3) measure the time it takes for www.mozilla.org to be displayed in the url bar > 4) measure the time it takes to match an entry yeah, we can. I think my patch do something similar. I'll clean it before the end of the time if i get any time for that.
Just a question, but how are you guys thinking about implementing the reporting structure for this? and will it be private or public?
(In reply to comment #3) > Just a question, but how are you guys thinking about implementing the reporting > structure for this? and will it be private or public? This bug blocks 538974 which is a fennecmark tracking bug
this would be in Fennecmark (per comment #1), and if we decide to add this to talos, it would be a talos test and the reporting,tracking would be just like all other talos stuff.
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.