Changes between Version 6 and Version 7 of QtWebKitProfilingSetup

Timestamp:

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

Author:

zecke@selfish.org

Comment:

--

QtWebKitProfilingSetup

@@ -27 +27 @@
 For testing the execution the [http://qt.nokia.com/doc/4.5/qtestlib-tutorial5.html built-in benchmarking] support of [http://qt.nokia.com/doc/4.5/qtestlib-manual.html 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.
 
+For looking into memory consumption the '''libmemusage.so''' library of glibc was selected. This library can be preloaded using `LD_PRELOAD=/lib/libmemusage.so` 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.
 
 
+=== Beagleboard setup ===
+
+The 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.
+
+The '''/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.
+
+=== Running the tests ===
+{{{
+# prepare the setup
+$ rm -rf /var/lib/oprofile
+$ opcontrol --start-daemon -p library -c 10
+
+# run the app once to force loading it from nfs into the cache
+$ ./tst_something
+
+# start profiling
+$ opcontrol --start
+$ ./tst_something -iterations enough
+
+# stop profiling
+$ opcontrol -h
+
+# generate reports
+$ opreport -l
+$ opreport -c ...
+
+# archiving it, it needs to be opimported on a x86 system
+$ oparchive -o /some/archive
+}}}