Changes between Version 6 and Version 7 of QtWebKitProfilingSetup

Sep 30, 2009 9:52:07 PM (15 years ago)



  • QtWebKitProfilingSetup

    v6 v7  
    2727For testing the execution the [ built-in benchmarking] support of [ QtTest] was used. This tool provides different event counters and options to control the iterations of the test. This can and should be used when executing the test once has too many variations.
     29For looking into memory consumption the '''''' library of glibc was selected. This library can be preloaded using `LD_PRELOAD=/lib/` and it can be instructed to safe a memory trace with `MEMUSAGE_OUTPUT=/my.trace`. The trace can be analyzed using the '''memusagestat''' of glibc or the performance suite.
     32=== Beagleboard setup ===
     34The beagleboard was configured to boot via nfsroot over usb-ethernet. This has the benefit of easily sharing files between the beagleboard and the host, e.g. for installing new software. The possible disadvantage is that during the tests new parts of the binary need to be loaded which will force to share the network between HTTP download and NFS.
     36The '''/etc/hosts''' file was adjusted to point to the server and a custom built version of Qt with `-fno-omit-frame-pointer` and the test applications were installed.
     38=== Running the tests ===
     40# prepare the setup
     41$ rm -rf /var/lib/oprofile
     42$ opcontrol --start-daemon -p library -c 10
     44# run the app once to force loading it from nfs into the cache
     45$ ./tst_something
     47# start profiling
     48$ opcontrol --start
     49$ ./tst_something -iterations enough
     51# stop profiling
     52$ opcontrol -h
     54# generate reports
     55$ opreport -l
     56$ opreport -c ...
     58# archiving it, it needs to be opimported on a x86 system
     59$ oparchive -o /some/archive