Changes between Version 3 and Version 4 of QtWebKitPerformanceToolBackLog:


Ignore:
Timestamp:
Oct 24, 2009 5:56:53 AM (11 years ago)
Author:
zecke@selfish.org
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • QtWebKitPerformanceToolBackLog:

    v3 v4  
    1010||memusage is not working on glibc/i686... this is making us blind on memory usage...||||
    1111||Benchmarks should generate more stable timing results.||||
    12 ||Change cycling, loading and scrolling to not use the _data and QFETCH but cycle through all sites in the QBENCHMARK and drop caches at the end of one iteration. This should be done because users will navigate from page to page instead of reloading everything and then going to the next one. And with the current QBENCHMARK we should see less variations when cycling through the whole set. Also maybe use an improved QBENCHMARK to log individual parts of the test...||[http://gitorious.org/qtwebkit/performance/commit/a80b4b31470e744fcf101d4f7fe5b4b5d98abc18 a80b4]||
     12||~~Minor patches to memprof to fix generation of images.~~||[http://gitorious.org/qtwebkit/performance/commit/ba418c4384f98010192e18c69b2b7c20e3c1629a ba418]||
     13||~~Fixed http server to nog hog CPU in case of cancelled requests~~||[http://gitorious.org/qtwebkit/performance/commit/4bc79d68bb20c39b3cb9a3cbf7440fc145999928 4bc79]||
     14||~~Change cycling, loading and scrolling to not use the _data and QFETCH but cycle through all sites in the QBENCHMARK and drop caches at the end of one iteration. This should be done because users will navigate from page to page instead of reloading everything and then going to the next one. And with the current QBENCHMARK we should see less variations when cycling through the whole set. Also maybe use an improved QBENCHMARK to log individual parts of the test...||[http://gitorious.org/qtwebkit/performance/commit/a80b4b31470e744fcf101d4f7fe5b4b5d98abc18 a80b4]||
    1315