Task notification vs queue performance in FreeRTOS - Visual Side-by-Side Comparison

Concept Flow - Task notification vs queue performance

Task A sends notification

↓

Task B waits for notification

↓

Notification received

↓

Task B processes event

↓

Task A sends data to queue

↓

Task B waits for queue data

↓

Data received from queue

↓

Task B processes data

Shows two flows: one where a task sends a notification and another where a task sends data via a queue, highlighting the difference in communication and processing.

Execution Sample

FreeRTOS

/* Task A sends notification */
xTaskNotifyGive(taskBHandle);

/* Task B waits for notification */
ulTaskNotifyTake(pdTRUE, portMAX_DELAY);

/* Task A sends data to queue */
xQueueSend(queueHandle, &data, portMAX_DELAY);

/* Task B receives data from queue */
xQueueReceive(queueHandle, &receivedData, portMAX_DELAY);

This code shows Task A sending a notification or queue data to Task B, and Task B waiting and receiving it.

Execution Table

Step	Action	Task A State	Task B State	Communication Method	Result
1	Task A sends notification	Notification sent	Waiting for notification	Notification	Notification sent to Task B
2	Task B receives notification	Idle	Notification received	Notification	Task B unblocked and processes event
3	Task A sends data to queue	Data enqueued	Waiting for queue data	Queue	Data placed in queue
4	Task B receives data from queue	Idle	Data received	Queue	Task B unblocked and processes data
5	End	Idle	Idle	Both	Communication complete

💡 Both methods complete communication; notification is faster with less overhead, queue handles data transfer.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Task A State	Idle	Notification sent	Idle	Data enqueued	Idle	Idle
Task B State	Waiting	Waiting for notification	Notification received	Waiting for queue data	Data received	Idle
Queue Content	Empty	Empty	Empty	Data present	Empty	Empty
Notification Flag	Clear	Set	Cleared	Clear	Clear	Clear

Key Moments - 3 Insights

Why is task notification faster than queue communication?

Task notification uses a direct signal without copying data, as shown in execution_table steps 1 and 2, making it faster with less overhead.

When should I use a queue instead of a task notification?

Use a queue when you need to send actual data, not just signals. Execution_table steps 3 and 4 show data being transferred via queue.

Does task notification support sending data like queues?

No, task notifications only send signals or simple values, not complex data. For data transfer, queues are needed as shown in the variable_tracker.

Visual Quiz - 3 Questions

Look at the execution_table, what is Task B state after Step 2?

A Notification received

B Waiting for notification

C Waiting for queue data

D Idle

💡 Hint

Check the 'Task B State' column at Step 2 in execution_table.

At which step does the queue contain data?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Queue Content' row in variable_tracker after Step 3.

If Task A sends notification twice before Task B receives it, what changes in the execution_table?

A Task B receives two notifications separately

B Task B state changes to waiting for queue data

C Only one notification is recorded; notifications do not queue

D Queue content increases

💡 Hint

Task notifications overwrite previous ones; see 'Notification Flag' in variable_tracker.

Concept Snapshot

Task notification is a lightweight signal from one task to another.
It is faster than queues because it avoids data copying.
Queues are used to send actual data between tasks.
Notifications do not store multiple signals; queues can buffer multiple items.
Use notifications for simple event signaling, queues for data transfer.

Full Transcript

This visual execution compares task notification and queue communication in FreeRTOS. Task A sends a notification or data to Task B. Notifications are simple signals that unblock Task B quickly without data copying, shown in steps 1 and 2. Queues transfer actual data, shown in steps 3 and 4, involving copying data into a buffer. Variable tracking shows Task A's and Task B's states, queue content, and notification flags changing step by step. Key moments clarify when to use notifications versus queues and why notifications are faster but limited. The quiz tests understanding of task states and data flow. The snapshot summarizes the main differences and use cases.