XRender benchmark
Zack Rusin
zrusin at trolltech.com
Thu Mar 16 17:50:33 PST 2006
Single, blue eyes, tall, great body, loves to travel and read. Looking for
serious and committed testers of a new application: XRenderBenchmark.
Rapid fire fashion:
Git respo: http://www.freedesktop.org/~zack/code/xrenderbenchmark/
tarball: http://www.freedesktop.org/~zack/xrenderbenchmark.tar.bz2
Screenshot: http://www.freedesktop.org/~zack/xenderbenchmark.png
Q: Why?
A: Because we have nothing to benchmark xrender across paths.
Q: What's going on there?
A: We test all operations in predefined set of scenarios. Scenarios are
created in testscenarios.cpp in create_test_scenarios function.
Q: How much wood could a woodchuck chuck?
A: That's a stupid question and I'm confused as to why would you even ask
that.
Q: What's missing?
A: It needs to output the cpu/card/driver info. And test scenarios need to be
added for different ways of handing alpha channel (component, external) and
operations with masks.
Q: How do I compile?
A: qmake; make; ./xrenderbenchmark
Q: What do I need?
A: Qt4 and Xserver.
Q: Why do you use Qt?
A: Because I didn't feel like screwing around with loading images through some
other external libraries. If someone feels like changing the code used for
reading images to use something else I'll remove Qt dependency, everything
else is C.
Zack
More information about the xorg
mailing list