Changes between Version 9 and Version 10 of QtWebKitPerformanceWork

Dec 21, 2009 5:35:30 PM (13 years ago)

Change formatting to outline mode


  • QtWebKitPerformanceWork

    v9 v10  
    1 == QtWebKit Performance Tuning Overview ==
     2= QtWebKit Performance Tuning Overview =
    3 === Prerequisites ===
     4== Prerequisites ==
    45You must have Python installed to run the included scripts. You can download it at [].
    6 === Getting the sourcecode, building and installing ===
     7== Getting the sourcecode, building and installing ==
    89The code can be checked out from the [ QtWebKit git repository], it requires Qt4.5.x or a Qt4.6 snapshot post Qt4.6 TP1.
    22 === Performance Utilities Overview ===
     23== Performance Utilities Overview ==
    2324The performance utilities contain utilities for the host, manual testing applications and benchmarking applications. All this is explained in depth on [wiki:QtWebKitPerformanceUtilities this] wiki site.
    25 === Running the tests ===
     26== Running the tests ==
    2627To run the tests one machine acting as a server and one machine acting as a client is needed, additionally mirrored web content must be available. This content can be provided on request, or it can be mirrored using the '''mirror''' application. For an overview of the utilities, how they work and what they should do please see the above section.
    28 ==== Preparing the server ====
     29=== Preparing the server ===
    2930On the server the '''http_server''' must be launched. root access is required to be able to bind to port 80 of the system. If a web server like apache is already running it must be stopped before starting the '''http_server'''. The server will abort when it fails to bind to the port. When starting the '''http_server''' pass the path to the database file to be used as the first command-line argument, e.g. `sudo ./http_server benchmark_content.db`.
    3435The tests can be executed by executing '''tst_loading''', '''tst_scrolling''' and '''tst_painting'''. During the test execution numbers are printed on the display. All the benchmarks are using the QtTest framework which allows to pass options like '''--iterations NUMBER''' to force repeating the loading more than once.
    37 === Running the tests with profiling on target hardware ===
     37== Running the tests with profiling on target hardware ==
    3838One of the reasons to create the test suite is to profile QtWebKit to identify possible improvements. Various approaches were compared and a in depth discussion on how to profile can be found on the [wiki:QtWebKitProfilingSetup Profiling Setup] page.
    40 === Performance backlog ===
     40== Performance backlog ==
    4141The Performance utilitiy has identified a set of work areas in the performance utilities themselves, QtWebKit and Qt. The backlog will contain a summary, and some description of how to carry out the change.
    4242See the [wiki:QtBackLog Qt/QtWebKit backlog] and [wiki:QtWebKitPerformanceToolBackLog: Performance backlog] for more information on work items.
    44 === Common Windows Errors ===
     44== Common Windows Errors ==
    46 ==== Microsoft Visual C++ Runtime Error when you run http_server ====
     46=== Microsoft Visual C++ Runtime Error when you run http_server ===
    4747If you see an error dialog with a message of the form: