1269948 - [Perf][google docs] 14.31%(3506 ms) slower than Chrome when opening 100 page mix content and undo/redo the keyword replacement

Status: RESOLVED WONTFIX

(Core :: General, defect)

Description

[Shako Ho]

# Test Case
STR
1. Launch the browser with blank page
2. input the google doc url with 100 page content ( 33 image, 33 table, others are txt with keyword)
3. Find the keyword and replace them to Keyword 2
4. undo all the replacement
5. redo all the replace ment
6. 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 | 27994.4444444444 ms
Chrome  | 24488.8888888888 ms

Comment 1

[Shako Ho]

test script can be found in here:
https://github.com/Mozilla-TWQA/Hasal/blob/master/tests/test_firefox_gdoc_update_undoredo_100.sikuli/test_firefox_gdoc_update_undoredo_100.py

Comment 2

[Shako Ho]

Attachment: Gecko profiler 1 ms interval

Comment 3

[Shako Ho]

Attachment: performance timing object

Comment 4

[Shako Ho]

Attachment: test_firefox_gdoc_update_undoredo_100_1463109404.har

Comment 5

[Shako Ho]

do the running time analysis between "navigationStart" and "domLoading"
 456  100%  |- Startup::XRE_Main/
 76   16.7% |  |- js::RunScript/
 57   12.5% |  |- nsRefreshDriver::Tick/
 33   7.2%  |  |  |- PresShell::Paint/
 20   4.4%  |  |  |- PresShell::Flush (Flush_Style)/
 38   8.3%  |  |- nsViewManager::DispatchEvent/
  7   1.5%  |  |- Timer::Fire/

Comment 6

[Shako Ho]

Do the running time analysis between "domLoading" and "loadEventEnd"
7568  100%  |- Startup::XRE_Main/
2451  32.4% |  |- Timer::Fire/
1877  24.8% |  |- nsInputStreamPump::OnInputStreamReady/
1714  22.6% |  |  |- nsInputStreamPump::OnStateStop/
 113  1.5%  |  |  |- nsInputStreamPump::OnStateStart/
1334  17.6% |  |- nsHtml5TreeOpExecutor::RunFlushLoop/
1153  15.2% |  |  |- nsJSUtils::EvaluateString/
 146  1.9%  |  |  |- EventDispatcher::Dispatch/
 702  9.3%  |  |- nsRefreshDriver::Tick/
 621  8.2%  |  |- js::RunScript/
 153   2%   |  |- nsJSUtils::EvaluateString/

Comment 7

[Shako Ho]

Do the running time analysis when replacing all keywords
8623  100%  |- Startup::XRE_Main/
1915  22.2% |  |- Timer::Fire/
1904  22.1% |  |- nsViewManager::DispatchEvent/
1310  15.2% |  |  |- EventDispatcher::Dispatch/
 462  5.4%  |  |- nsRefreshDriver::Tick/
 41   0.5%  |  |- js::RunScript/

Comment 8

[Shako Ho]

Do the running time analysis when undo action
 149  100%  |- Startup::XRE_Main/
 16   10.7% |  |- nsRefreshDriver::Tick/
 15   10.1% |  |- nsViewManager::DispatchEvent/
 15   10.1% |  |  |- EventDispatcher::Dispatch/
 12   8.1%  |  |- Timer::Fire/
  1   0.7%  |  |- js::RunScript/

Comment 9

[Shako Ho]

Do the running time analysis when redo action
 152  100%  |- Startup::XRE_Main/
 12   7.9%  |  |- nsViewManager::DispatchEvent/
 12   7.9%  |  |  |- EventDispatcher::Dispatch/
  2   1.3%  |  |- Timer::Fire/
  1   0.7%  |  |- nsRefreshDriver::Tick/
  1   0.7%  |  |- js::RunScript/

Comment 10

[Bobby Chien]

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.