Changes between Version 2 and Version 3 of QtWebKitPerformanceWork


Ignore:
Timestamp:
Sep 29, 2009 11:36:52 PM (11 years ago)
Author:
zecke@selfish.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QtWebKitPerformanceWork

    v2 v3  
    1616
    1717=== Running the tests ===
     18To 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.
    1819
    19 === Adding a new test ===
     20==== Preparing the server ====
     21On 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 to be used database to the process, e.g. `sudo ./http_server benchmark_content.db`.
    2022
     23==== Preparing the client ====
     24On the client the '''/etc/hosts''' file must be edited. For the mirrored content it must point to the IP address of the server. In the '''mirror/''' is a script called '''create_hosts.py''' which helps to create the host entries for a given database and IP address. The script is requiring python so it might be necessary to execute the script on the desktop and append the output to the '''/etc/hosts''' of the target.
     25
     26The 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 '''--iterations NUMBER''' to force repeating the loading more than once.
     27
     28
     29=== Running the tests with profiling on target hardware ===
     30One of the reasons to great 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.
    2131
    2232=== Performance backlog ===