b1fd9a93b9
This test is doing a brute-force mapping. Coupled with changes to QCOMPARE last year, this now allocates and deallocates a lot of memory per iteration. On my Sandybridge, it takes two minutes to run: 111136.781153 task-clock # 0.999 CPUs utilized 371,692,633,238 cycles # 3.344 GHz 182,641,818,708 stalled-cycles-frontend # 49.14% frontend cycles idle 57,951,552,830 stalled-cycles-backend # 15.59% backend cycles idle 477,216,332,971 instructions # 1.28 insns per cycle # 0.38 stalled cycles per insn 86,959,637,669 branches # 782.456 M/sec 309,185,237 branch-misses # 0.36% of all branches 111.264868818 seconds time elapsed Changing the iteration step from 1 to 5 reduces the runtime to about 5 seconds. Change-Id: I9cad6f85f535f472319da7cd6c4aa28e12ddf1b7 Reviewed-by: Jason McDonald <jason.mcdonald@nokia.com> Reviewed-by: Lars Knoll <lars.knoll@nokia.com> |
||
---|---|---|
.. | ||
qgraphicsanchorlayout | ||
qgraphicsanchorlayout1 | ||
qgraphicseffectsource | ||
qgraphicsgridlayout | ||
qgraphicsitem | ||
qgraphicsitemanimation | ||
qgraphicslayout | ||
qgraphicslayoutitem | ||
qgraphicslinearlayout | ||
qgraphicsobject | ||
qgraphicspixmapitem | ||
qgraphicspolygonitem | ||
qgraphicsproxywidget | ||
qgraphicsscene | ||
qgraphicssceneindex | ||
qgraphicstransform | ||
qgraphicsview | ||
qgraphicswidget | ||
graphicsview.pro |