It seems equally slow when running debug and release libs, but will double
check later this weekend to make sure it's not user-error. I think it has more
to do with running with a video card that doesn't provide much (if any?)
hardware acceleration. But I was assuming that even in that case that QML2
would be just as good as QML1. Clearly something is causing that to not be the
case.
What's the expectation when using video cards that don't offer OpenGL hardware
acceleration?
-Todd
-Original Message-
From: Storm-Olsen Marius (Nokia-MP/Austin)
Sent: Saturday, January 14, 2012 9:12 AM
To: development@qt-project.org; Rose Todd (Nokia-M/Alpharetta)
Subject: Re: [Development] Status of QtDeclarative on Windows?
Are you sure you are at least running the release version of your application?
Debug version uses the debug CRT libs (and a debug Qt which does the
same), so everything will be a lot slower than the end product.
You cannot really evaluate performance with debug builds.
--
Sent from my Nokia N9
On 1/13/12 23:12 ext todd.r...@nokia.com wrote:
Just for fun I’ve been playing with a medium-sized QML app that we had
written for 4.7/Symbian and porting it to Qt5/QML2. Mostly have been
working on Linux but the past few days I finally got around to compiling Qt5
on Windows and playing around with the project enough so that it would
compile and run under qmlscene (it’s mostly qml/js with a C++ plugin module
as well).
Anyway, the performance on my Windows box is horrible. ListView scrolling,
image loading, animations, everything is like it’s running in quicksand. Is
this
expected? If not, what do I need to do to in order to troubleshoot? This
machine is relatively old and has a crappy video card (older Nvidia Quadro),
but it should be more than good enough to run this app smoothly. Any tips
or tricks to enable extra debug tracing?
Thanks,
Todd
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
