Skip to main content

QT - foreach algoriithm with const references performance improvement

Today I would like to show you optimal way of using foreach QT algorithm. I will show you why we should pass elements of foreach algorithm by const reference instead of passing them by value.

Let me explain it on the below example:
Output of this example is:
In point I we are creating 3 objects of MyClass class and push them to myClasses QList element.

In point II we are using QT foreach algorithm to invoke getValue() method for each object from myClasses list. As you can see on output text for that part of code we are invoking copy constructor before and destructor after invoking getValue() function. It is because we are passing each myClasses list element to foreach algorithm by value. Therefore we are copying that element at the beginning of foreach loop step and removing them (destructing) at the end. This is inefficient solution, especially when class of object being copied is big. It decreases performance. of our application.

Solution for that inefficiency is passing elements to foreach QT algorithm by const reference, as shown on point III. Thanks to that we are doing our operations on existing objects from myClasses list without copying. As you can see on the output text we are not invoking constructor and destructor foreach element here, so performance is better.

Code of this example you can find on our GitHub account here: https://github.com/xmementoit/CppAdventureExamples/tree/master/qt/foreachRefCount

Comments

  1. Good explanation. Good to know this advantage of const references in QT foreach algorithm.

    ReplyDelete

Post a Comment

Popular posts from this blog

C++ Multithreading - Race conditions

In the previous C++ Multithreading article I presented you how to pass parameters between threads. Take a detail look on the output of that example once again: In the first line of that output you can notice that output text from two threads is mixed. You are probably wondering why it happens? It is because we are not protecting resources which are shared by two threads (in this example cout stream is shared in both threads) which causes multithreading's phenomenon called race condition . Because threads switching and accessing to shared resources are managed by operating system we do not know when std::cout stream will be accessed by main thread and when it will be accessed by second thread. Therefore in the previous article I mentioned that output of the example can be little different on your computer than my output example. What's more it is possible that this output will be different for few consecutive invoking of the example on the same machine. It is beca...

GDB Automatic Deadlock Detector

Have you ever had a problem with detection deadlock between threads in your C/C++ application? Would you like to do that automatically? Try this GDB Automatic Deadlock Detector from my github: GDB Automatic Deadlock Detector Picture source: http://csunplugged.org/wp-content/uploads/2015/03/deadlock.jpg1286488735

Blog's new layout

As you noticed this blog has new layout from today. I hope you like it. I think new layout looks better and more modern than previous one. Please, write you opinion about new layout in comments. If you have some ideas how to make this blog better, all ideas are welcomed. Enjoy new layout and blog articles.