Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Delphi Programming: A Complete Reference Guide

You're reading from   Mastering Delphi Programming: A Complete Reference Guide Learn all about building fast, scalable, and high performing applications with Delphi

Arrow left icon
Product type Course
Published in Nov 2019
Publisher Packt
ISBN-13 9781838989118
Length 674 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Primož Gabrijelčič Primož Gabrijelčič
Author Profile Icon Primož Gabrijelčič
Primož Gabrijelčič
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. About Performance FREE CHAPTER 2. Fixing the Algorithm 3. Fine-Tuning the Code 4. Memory Management 5. Getting Started with the Parallel World 6. Working with Parallel Tools 7. Exploring Parallel Practices 8. Using External Libraries 9. Introduction to Patterns 10. Singleton, Dependency Injection, Lazy Initialization, and Object Pool 11. Factory Method, Abstract Factory, Prototype, and Builder 12. Composite, Flyweight, Marker Interface, and Bridge 13. Adapter, Proxy, Decorator, and Facade 14. Nullable Value, Template Method, Command, and State 15. Iterator, Visitor, Observer, and Memento 16. Locking Patterns 17. Thread pool, Messaging, Future and Pipeline 18. Other Books You May Enjoy

Memory allocation in a parallel world

We've seen how FastMM boosts the reallocation speed. Let's take a look at another optimization which helps a lot when you write a multithreaded code—as we will in the next three chapters.

The life of a memory manager is simple when there is only one thread of execution inside a program. When the memory manager is dealing out the memory, it can be perfectly safe in the knowledge that nothing can interrupt it in this work.

When we deal with parallel processing, however, multiple paths of execution simultaneously execute the same program and work on the same data. (We call them threads and I'll explain them in the next chapter.) Because of that, life from the memory manager's perspective suddenly becomes very dangerous.

For example, let's assume that one thread wants some memory. The memory manager finds a free...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime