Walter Chen[:ypwalter][:wachen] Reporter
	Description • 7 years ago

STR:
1. Open Amazon homepage
2. type 'm' in search field
3. type down key twice
4. type down key

Reports: https://goo.gl/d6OAQK
Notes: https://docs.google.com/spreadsheets/d/1MsTK1FW88wuLd25A18HG2KqpjYJnvrxGM9a6MeZp35w/edit#gid=256706414

Firefox Profile:
https://perfht.ml/2qmB32V

Chrome Tracing Log:
https://goo.gl/bozPX4

	MarkYen
	Comment 1 • 7 years ago

Short Gecko Profile(cover only Input Lantency action):
https://perfht.ml/2qMYP8s

	Andrew Overholt [:overholt]
	Comment 2 • 7 years ago

I can't tell if (or how much) worse we are here, Walter: https://github.com/Mozilla-TWQA/Hasal-result/blob/master/20170516/amazon/win10/amazon_ail_select_search_suggestion.ipynb

	Walter Chen[:ypwalter][:wachen] Reporter
	Comment 3 • 7 years ago

Hi, Andrew,

I think we can try to look at the data deeper. There are plenty of ways to understand the data.
1. median value of input latency time is the same for firefox and chrome.
2. average time for firefox is almost 17 comparing to chrome's 9.6
3. max time of firefox is 1.5 times more than chrome
4. std time for firefox is higher
5. firefox have 25% of all running times to have worse performance than chrome (75%: chrome 5.55 vs firefox 11.11)

However, they have one outlier in each browser. It's affecting med, avg, max, and std values. If you remove the outlier and look at the data again. The results are almost the same, but firefox is still having a little bit more slack in performance.

Yet, 2 browsers did perform almost the same.
Hope this clarify things out.

	Kan-Ru Chen [:kanru] (UTC+9)
	Comment 4 • 7 years ago

I'm closing this one since Firefox is already faster than or on par with Chrome in this case.