How to get qtdemo with reasonable speed?

[ponto]

Are we talking about openGL? What's the output of:
glxinfo | grep direct

Here is the output

ponto@burns:~> glxinfo | grep direct
direct rendering: Yes

ponto@burns:~> glxinfo | grep direct
direct rendering: Yes

To copy to clipboard, switch view to plain text mode 

I do not think that opengl is a problem here, because games like Unreal Tournament 2003 are quite fast here. I also do not know whether the qtdemo app uses opengl.

[wysota]

Did you compile the demo in debug or release mode? (Simply speaking, is the binary of it "huge" (2MB) or "small" (200kB)?) It might be compiled in debug mode, which causes a major slowdown.

[ponto]

Did you compile the demo in debug or release mode? (Simply speaking, is the binary of it "huge" (2MB) or "small" (200kB)?) It might be compiled in debug mode, which causes a major slowdown.

I see that the qtdemo executable itself is linked against debug versions of the Qt libraries. Howver the demos themselves are linked against the release libraries. I also checked the compilation process and see that optimized binaries are build.

[wysota]

But is it just the qtdemo that is slow or all examples are slow?

[ponto]

But is it just the qtdemo that is slow or all examples are slow?

Most examples are as slow as qtdemo. For example the composite demo is really slow. Also slow are deform and pathstroke.
Mainwindow is not really slow but too slow for the shown effect.

[wysota]

Composite can be a bit slow, although I don't have direct rendering working, so that may be because of the driver.

[nuntius]

Disclaimer: X11 only

The source for qtdemo is in QTDIR/examples/tools/qtdemo.
Search for "slow" in displaywidget.cpp.
This message popped up *once* for me, I responded properly, and qtdemo ran fast. Every other time, its been slow as molasses.