Book Image

Delphi High Performance - Second Edition

By : Primož Gabrijelčič
5 (1)
Book Image

Delphi High Performance - Second Edition

5 (1)
By: Primož Gabrijelčič

Overview of this book

Performance matters! Users hate to use programs that are not responsive to interactions or run too slow to be useful. While becoming a programmer is simple enough, you require dedication and hard work to achieve an advanced level of programming proficiency where you know how to write fast code. This book begins by helping you explore algorithms and algorithmic complexity and continues by describing tools that can help you find slow parts of your code. Subsequent chapters will provide you with practical ideas about optimizing code by doing less work or doing it in a smarter way. The book also teaches you how to use optimized data structures from the Spring4D library, along with exploring data structures that are not part of the standard Delphi runtime library. The second part of the book talks about parallel programming. You’ll learn about the problems that only occur in multithreaded code and explore various approaches to fixing them effectively. The concluding chapters provide instructions on writing parallel code in different ways – by using basic threading support or focusing on advanced concepts such as tasks and parallel patterns. By the end of this book, you’ll have learned to look at your programs from a totally different perspective and will be equipped to effortlessly make your code faster than it is now.
Table of Contents (15 chapters)

About performance

As I stated in the opening statement of this book—performance matters. But what exactly is performance? What do we mean when we use this word? Sometimes, we just want to say that the program runs so fast that the users don’t detect any delays. We can say that the program is not lagging and that the user interface does not block. In other situations, performance means that a program finishes its execution quickly, or that a server can handle a large number of clients.

Knowing what we mean when we use the word will help us determine the best way to fix the problem. Whatever the approach will be, we still have to find out why the application is not performing as we expect. The first suspect should always be the algorithm, and to examine it, we need to know more about how algorithms behave.

Algorithms are all different. What we want to know about them when we are designing a program is how they behave when their input set gets larger and larger. Some...