Optimize: use std::vector instead of QVector for the change queues.

Note that QVector::clear() frees memory, as does resize(0) now
apparently. This triggers repeated allocations after we distributed
the changes. Using std::vector instead, we can reuse the memory
leading to a noticeable performance improvement.

Change-Id: Ib08795a7ba3f893c13dad29f50641e4e2dc924e4
Reviewed-by: Paul Lemire <paul.lemire@kdab.com>
Reviewed-by: Sean Harmer <sean.harmer@kdab.com>

1 files changed, 1 insertions, 1 deletions

diff --git a/src/core/qchangearbiter_p.h b/src/core/qchangearbiter_p.h
index 83dfdd911..db44acaa2 100644
--- a/src/core/qchangearbiter_p.h
+++ b/src/core/qchangearbiter_p.h
@@ -106,7 +106,7 @@ public:
     static void destroyThreadLocalChangeQueue(void *changeArbiter);
 
 protected:
-    typedef QVector<QSceneChangePtr> ChangeQueue;
+    typedef std::vector<QSceneChangePtr> ChangeQueue;
     typedef QPair<ChangeFlags, QObserverInterface *> QObserverPair;
     typedef QList<QObserverPair> QObserverList;