Grand Central Dispatch (GCD)

Ever used an app that froze when loading data? That's often due to blocking the main thread.

The main thread is where all UI updates and user interactions happen. If you perform a long-running task there, your app becomes unresponsive.

Concurrency means running multiple tasks seemingly at the same time. This keeps the main thread free, ensuring a smooth user experience.

Grand Central Dispatch (GCD) is Apple's powerful low-level API for managing concurrent operations. It's built on top of C and blocks, and makes it easy to perform tasks asynchronously.

GCD helps you run code concurrently by managing dispatch queues. You tell GCD what tasks to run, and it decides when and how to execute them on available processor cores.

GCD uses dispatch queues to manage tasks. Think of a queue as a line of tasks waiting to be executed.

• Serial Queues: Tasks run one by one, in the order they were added. Each serial queue processes its tasks sequentially.
• Concurrent Queues: Tasks are started in the order they are added, but can run at the same time (concurrently). The order of completion is not guaranteed.

Every iOS application has a special serial queue called the main dispatch queue. This is where all UI updates must happen.

If you try to update the UI from a background thread, your app might crash or behave unexpectedly. Always switch back to the main queue for UI changes.

You access it using dispatch_get_main_queue().

GCD provides several global concurrent queues that you can use for background tasks. These queues are managed by the system and optimized for performance.

They differ by their Quality of Service (QoS) class, which indicates the priority of tasks:

• .userInteractive: UI-related, highest priority.
• .userInitiated: User-requested tasks.
• .utility: Long-running, non-urgent tasks.
• .background: Maintenance, lowest priority.

The most common way to use GCD is with dispatch_async. This function adds a task (a block of code) to a queue and immediately returns, allowing the calling code to continue execution.

The task will then run on a separate thread in the background. This is perfect for operations that don't need to block the main thread, like network requests or heavy computations.

While dispatch_async is great for non-blocking operations, sometimes you need to wait for a task to complete before continuing. That's where dispatch_sync comes in.

dispatch_sync adds a task to a queue and then blocks the current thread until that task finishes execution. Be careful: never call dispatch_sync on the current queue, as it will cause a deadlock!

A common pattern in iOS apps is to perform a long-running task in the background and then update the UI once it's done. This prevents the UI from freezing.

You achieve this by dispatching the background task to a global concurrent queue, and then dispatching the UI update task to the main queue.

Sometimes you need to schedule a task to run after a certain delay. GCD provides dispatch_after for this purpose.

It's important to note that dispatch_after is not a real-time timer. It simply adds a block to the specified queue after a minimum delay. The exact execution time depends on the queue's activity.

Great job! You've learned the fundamentals of Grand Central Dispatch.

• GCD helps manage concurrent tasks to keep your app responsive.
• Dispatch queues (serial and concurrent) control task execution.
• The main queue is for UI updates, always accessed via dispatch_async.
• Global concurrent queues are for background work.
• dispatch_async runs tasks without blocking, dispatch_sync waits for tasks.

Mastering GCD is crucial for building high-performance, responsive iOS applications.