Book Image

Hands-On High Performance Programming with Qt 5

By : Marek Krajewski
5 (1)
Book Image

Hands-On High Performance Programming with Qt 5

5 (1)
By: Marek Krajewski

Overview of this book

Achieving efficient code through performance tuning is one of the key challenges faced by many programmers. This book looks at Qt programming from a performance perspective. You'll explore the performance problems encountered when using the Qt framework and means and ways to resolve them and optimize performance. The book highlights performance improvements and new features released in Qt 5.9, Qt 5.11, and 5.12 (LTE). You'll master general computer performance best practices and tools, which can help you identify the reasons behind low performance, and the most common performance pitfalls experienced when using the Qt framework. In the following chapters, you’ll explore multithreading and asynchronous programming with C++ and Qt and learn the importance and efficient use of data structures. You'll also get the opportunity to work through techniques such as memory management and design guidelines, which are essential to improve application performance. Comprehensive sections that cover all these concepts will prepare you for gaining hands-on experience of some of Qt's most exciting application fields - the mobile and embedded development domains. By the end of this book, you'll be ready to build Qt applications that are more efficient, concurrent, and performance-oriented in nature
Table of Contents (14 chapters)

Summary

In this chapter, we looked at some real cases that the author encountered in his work. Was it only a mere listing of some unrelated cases or did we learn something from them?

For me, the recurrent theme in each of these cases was how unexpected these problems were. Some quite reasonable assumptions were made, the software was written, but then it turned out that, despite the whole reasoning there were performance problems showing up! So, one of the lessons from these problem cases is that you'll never be sure until you've comprehensively tested your system.

The other surprise is how often the underlying reason is very simple, but not exactly trivial. This includes situations where you have a poorly scaling data structure, a linear or a quadratic algorithm, or a bad locking strategy. However, this is also encouraging once we are able to determine the...