Bug 34501 - [Qt] Poor Performance of QtWebKit layouting on Mac
Summary: [Qt] Poor Performance of QtWebKit layouting on Mac
Status: RESOLVED DUPLICATE of bug 38179
Alias: None
Product: WebKit
Classification: Unclassified
Component: Platform (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.6
: P2 Normal
Assignee: Benjamin Poulain
URL: http://gist.github.com/raw/288082/95e...
Keywords: Performance, Qt
Depends on: 31719
Blocks:
  Show dependency treegraph
 
Reported: 2010-02-02 13:26 PST by Justin Camerer
Modified: 2010-04-27 04:15 PDT (History)
1 user (show)

See Also:


Attachments
tarball of some profiling output of webkit vs qtwebkit (13.44 MB, application/x-gzip)
2010-02-02 13:26 PST, Justin Camerer
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Camerer 2010-02-02 13:26:04 PST
Created attachment 47971 [details]
tarball of some profiling output of webkit vs qtwebkit

In comparison to Safari or Chrome, QtWebKit is incredibly slow in a few areas. The main problems are:

  * Scroll speed (causes dom manipulation in this example)
  * Window resizing
  * CSS resizable columns of from “resize: horizontal”

I am attempting to create a cross platform application that depends on these working smoothly. Have these problems surfaced before?
Comment 1 Benjamin Poulain 2010-03-06 09:19:54 PST
  * Scroll speed (causes dom manipulation in this example)

This is a known issue. On Mac, with Qt, the scroll() function does not blit the pixels, it forces a full repaint of the view.

This is not a WebKit issue, and the developers of Qt are aware of the problem.
You can try to render the web page with OpenGL. OpenGL always do full update, but the speed of rendering should compensate.


  * Window resizing
  * CSS resizable columns of from “resize: horizontal”

These are layouting problems. I did not know there was an issue on Mac, some profiling will be needed.
Comment 2 Benjamin Poulain 2010-04-27 04:15:24 PDT

*** This bug has been marked as a duplicate of bug 38179 ***