Closed
Bug 1269665
Opened 9 years ago
Closed 8 years ago
[Perf][google docs] 0.48%(1672ms) slower than Chrome when creating 50 page content with pageup and pageend action
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
platform-rel | --- | ? |
People
(Reporter: sho, Assigned: sho)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Whiteboard: [platform-rel-Google][platform-rel-GoogleDocs])
User Story
You can find all test scripts on github link: https://github.com/mozilla-twqa/hasal And you can also find the running script name in comments for example: test scripts: test_chrome_gdoc_create_txt_1 then you can specify the test script name on suite.txt and run it
Attachments
(4 files)
# Test Case
STR
1. Launch the browser with blank page
2. input the blank google doc page url
3. input 1 page txt
4. press page up
5. input 1 image
6. press ctrl+end(to the last page)
7. input 1 page txt
8. input 1 table
9. repeat step 3 to 8 17 times
10. close the browser
# Hardware
OS: Ubuntu 14.04 LTS 64-bit
CPU: i7-3770 3.4GMhz
Memory: 16GB Ram
Hard Drive: 1TB SATA HDD
Graphics: GK107 [GeForce GT 640]/ GF108 [GeForce GT 440/630]
# Browsers
Firefox version: 45.0.2
Chrome version: 50.0.2661.75
# Result
Browser | Run time (median value)
Firefox | 352683.333333333 ms
Chrome | 351011.111111111 ms
Blocks: Meta-Hasal-GDoc
Updated•9 years ago
|
Product: Firefox → Core
Updated•9 years ago
|
Version: unspecified → 45 Branch
running time analysis between domloading and loadeventend
3900 100% |- Startup::XRE_Main
1500 38.5% | |- nsInputStreamPump::OnInputStreamReady
1350 34.6% | | |- nsInputStreamPump::OnStateStop
100 2.6% | | |- nsInputStreamPump::OnStateStart
640 16.4% | |- js::RunScript
620 15.9% | |- nsHtml5TreeOpExecutor::RunFlushLoop
460 11.8% | | |- nsJSUtils::EvaluateString
130 3.3% | | |- EventDispatcher::Dispatch
470 12.1% | |- nsRefreshDriver::Tick
240 6.2% | |- Timer::Fire
running time analysis when creating table
5450 100% |- Startup::XRE_Main
950 17.4% | |- nsViewManager::DispatchEvent
950 17.4% | | |- EventDispatcher::Dispatch
410 7.5% | |- nsRefreshDriver::Tick
120 2.2% | |- Timer::Fire
70 1.3% | |- js::RunScript
running time analysis when inserting image
17460 100% |- Startup::XRE_Main
1070 6.1% | |- nsViewManager::DispatchEvent
740 4.2% | | |- EventDispatcher::Dispatch
1030 5.9% | |- nsRefreshDriver::Tick
460 2.6% | |- js::RunScript
390 2.2% | |- Timer::Fire
running time analysis when page end action
150 100% |- Startup::XRE_Main
10 6.7% | |- nsViewManager::DispatchEvent
10 6.7% | | |- EventDispatcher::Dispatch
Assignee | ||
Comment 10•9 years ago
|
||
running time analysis when page up action
140 100% |- Startup::XRE_Main
30 21.4% | |- nsViewManager::DispatchEvent
30 21.4% | | |- EventDispatcher::Dispatch
10 7.1% | |- nsRefreshDriver::Tick
Assignee | ||
Comment 11•9 years ago
|
||
running time analysis when page up action
2 100% |- Startup::XRE_Main
2 100% | |- Timer::Fire
Assignee | ||
Comment 12•9 years ago
|
||
unning time analysis when select all
1870 100% |- Startup::XRE_Main
900 48.1% | |- nsViewManager::DispatchEvent
830 44.4% | | |- EventDispatcher::Dispatch
570 30.5% | |- nsRefreshDriver::Tick
300 16% | |- Timer::Fire
Assignee | ||
Comment 13•9 years ago
|
||
running time analysis when typing
7700 100% |- Startup::XRE_Main
2930 38.1% | |- nsViewManager::DispatchEvent
2910 37.8% | | |- EventDispatcher::Dispatch
860 11.2% | |- nsRefreshDriver::Tick
60 0.8% | |- js::RunScript
Updated•8 years ago
|
Whiteboard: [platform-rel-Google][platform-rel-GoogleDocs]
Updated•8 years ago
|
platform-rel: --- → ?
Comment 14•8 years ago
|
||
Mark as minor case, and marked wontfix in this iteration. Revisit here if necessary.
This bug fixing iteration will focus on critical bug 1264535, bug 1269666, bug 1269684, bug 1269690, bug 1269695, bug 1269698.
Severity: normal → minor
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•