[Webkit-unassigned] [Bug 143868] [GTK] Slow to render simple page with 20.000 lines

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=143868

Milan Crha <mcrha at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #251011|0                           |1
        is obsolete|                            |

--- Comment #4 from Milan Crha <mcrha at redhat.com> ---
Created attachment 251013
  --> https://bugs.webkit.org/attachment.cgi?id=251013&action=review
test-wk2.c

Updated test-wk2.c with measured times.

The webkitgtk4-2.8.1-1.fc22.x86_64 shows these times:
  load_changed_cb: WEBKIT_LOAD_STARTED after 0.257252s
  load_changed_cb: WEBKIT_LOAD_COMMITTED after 0.268599s
  load_changed_cb: WEBKIT_LOAD_FINISHED after 2.59222s

while webkitgtk4-2.6.5-3.fc21.x86_64 shows:
  load_changed_cb: WEBKIT_LOAD_STARTED after 0.098319s
  load_changed_cb: WEBKIT_LOAD_COMMITTED after 0.101146s
  load_changed_cb: WEBKIT_LOAD_FINISHED after 6.49957s

thus you clearly made some improvements already.

I suggest to run the test application under callgrind:
   $ G_SLICE=always-malloc valgrind --tool=callgrind --trace-children=yes ./test-wk2

then use a tool like kcachegrind to examine the bottlenecks. I see (with the 2.6.5) 100 and 200 million-times called functions in the web process, which feels like a room for improvements, especially when the HTML document contains only 20K lines with a bit more tags in total.

I didn't run the callgrind with the 4.8.1, it's a virtual machine and there is not enough place for the debug info, without which the callgrind log is useless.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150417/c50d607e/attachment.html>