Dispatching jobs in Laravel - Performance & Optimization

Performance: Dispatching jobs

HIGH IMPACT

This affects how quickly the main web request responds by offloading work to background processes, improving user experience and server responsiveness.

Handling time-consuming tasks during a web request

Laravel

<?php
use App\Jobs\ProcessLargeFile;

public function store(Request $request) {
    ProcessLargeFile::dispatch($request->file);
    return response()->json(['status' => 'queued']);
}

// Job class handles processing asynchronously

Dispatching the job queues the task to run in the background, allowing the HTTP response to return immediately.

📈 Performance GainReduces blocking time to under 100ms, improving INP and user experience.

Handling time-consuming tasks during a web request

Laravel

<?php
// Controller method
public function store(Request $request) {
    // Heavy task directly in request
    $this->processLargeFile($request->file);
    return response()->json(['status' => 'done']);
}

private function processLargeFile($file) {
    // Simulate heavy processing
    sleep(10);
    // Process file logic
}

Running heavy tasks synchronously blocks the HTTP response, causing slow page loads and poor user experience.

📉 Performance CostBlocks rendering for 10+ seconds, increasing INP and causing user frustration.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Synchronous heavy task in request	N/A	Blocks main thread	Delays paint	[X] Bad
Dispatch job to queue	N/A	No blocking	Fast paint	[OK] Good

Rendering Pipeline

Dispatching jobs moves heavy processing out of the critical rendering path, so the browser can receive and paint the page faster.

→Network

→JavaScript Execution

→Rendering

⚠️ BottleneckSynchronous heavy processing during request delays network response and blocks rendering.

Core Web Vital Affected

INP

This affects how quickly the main web request responds by offloading work to background processes, improving user experience and server responsiveness.

Optimization Tips

1Always dispatch heavy or long-running tasks to background jobs to keep HTTP requests fast.

2Avoid synchronous processing of large files or external API calls during web requests.

3Monitor performance with DevTools to ensure no long blocking tasks delay rendering.

Performance Quiz - 3 Questions

What is the main performance benefit of dispatching jobs in Laravel?

A It moves heavy tasks out of the HTTP request to improve response time.

B It reduces the size of the JavaScript bundle sent to the browser.

C It improves CSS selector matching speed.

D It decreases the number of DOM nodes rendered.

DevTools: Performance

How to check: Record a performance profile while triggering the request. Look for long tasks blocking the main thread.

What to look for: Long blocking tasks over 1 second indicate synchronous heavy processing; short tasks indicate good async dispatch.

Practice

1. What is the main purpose of dispatching jobs in Laravel?

easy

A. To handle user authentication

B. To run tasks in the background without blocking user requests

C. To create database tables automatically

D. To directly output data to the browser

Solution

1. Step 1: Understand what dispatching jobs means

   Dispatching jobs means sending tasks to run in the background, separate from the main app flow.

2. Step 2: Identify the benefit of background jobs

   Running tasks in the background improves app speed and user experience by not blocking user requests.

3. Final Answer:

   To run tasks in the background without blocking user requests -> Option B

4. Quick Check:

   Dispatching jobs = background tasks [OK]

Hint: Jobs run in background to keep app fast and responsive [OK]

Common Mistakes:

• Thinking dispatching jobs outputs data immediately
• Confusing jobs with database migrations
• Assuming jobs handle user login

2. Which is the correct way to dispatch a job called SendEmailJob in Laravel?

easy

A. SendEmailJob.dispatch();

B. dispatch SendEmailJob();

C. SendEmailJob::dispatch();

D. dispatch::SendEmailJob();

Solution

1. Step 1: Recall Laravel job dispatch syntax

   Laravel uses the static method ::dispatch() on the job class to send it to the queue.

2. Step 2: Match the syntax to the options

   SendEmailJob::dispatch(); uses SendEmailJob::dispatch(); which is the correct Laravel syntax.

3. Final Answer:

   SendEmailJob::dispatch(); -> Option C

4. Quick Check:

   JobClass::dispatch() = correct syntax [OK]

Hint: Use ClassName::dispatch() to send jobs [OK]

Common Mistakes:

• Using dot instead of double colon for static call
• Trying to call dispatch as a function without ::
• Incorrect order or missing parentheses

3. Given this code:

SendReportJob::dispatch();
return 'Report sent';

What will the user see immediately after this code runs?

medium

A. The report is sent and user sees 'Report sent' immediately

B. The user waits until the report is sent, then sees 'Report sent'

C. An error because dispatch() is not a valid method

D. Nothing happens because dispatch() does not run the job

Solution

1. Step 1: Understand dispatch() behavior

   Dispatching a job sends it to the queue to run in the background immediately without blocking.

2. Step 2: Analyze the return statement

   The return 'Report sent' runs right after dispatch(), so the user sees this message immediately.

3. Final Answer:

   The report is sent and user sees 'Report sent' immediately -> Option A

4. Quick Check:

   dispatch() runs background job, return runs immediately [OK]

Hint: dispatch() queues job; return runs right after [OK]

Common Mistakes:

• Thinking dispatch() waits for job to finish
• Assuming dispatch() causes an error
• Believing dispatch() does nothing

4. What is wrong with this code snippet?

dispatch SendEmailJob();

medium

A. dispatch is not a function, should use SendEmailJob::dispatch()

B. Missing parentheses after dispatch

C. SendEmailJob must be instantiated with new keyword

D. dispatch should be lowercase

Solution

1. Step 1: Check dispatch usage

   In Laravel, dispatching a job is done by calling ::dispatch() on the job class, not by calling dispatch as a function.

2. Step 2: Identify the error in the code

   The code tries to call dispatch as a function without parentheses and without using the static method on the job class.

3. Final Answer:

   dispatch is not a function, should use SendEmailJob::dispatch() -> Option A

4. Quick Check:

   Use JobClass::dispatch() not dispatch function [OK]

Hint: dispatch() is a static method on job class, not a function [OK]

Common Mistakes:

• Calling dispatch as a standalone function
• Forgetting :: before dispatch
• Trying to instantiate job without dispatch

5. You want to dispatch a job ProcessOrderJob with an order ID parameter 123. Which code correctly dispatches this job with the parameter?

hard

A. ProcessOrderJob::dispatch()->with(123);

B. dispatch(ProcessOrderJob(123));

C. ProcessOrderJob->dispatch(123);

D. ProcessOrderJob::dispatch(123);

Solution

1. Step 1: Understand how to pass parameters to jobs

   Jobs accept constructor parameters, and dispatch() forwards them to the constructor.

2. Step 2: Match correct syntax

   ProcessOrderJob::dispatch(123); calls ProcessOrderJob::dispatch(123); which passes 123 to the job constructor correctly.

3. Final Answer:

   ProcessOrderJob::dispatch(123); -> Option D

4. Quick Check:

   dispatch(params) passes args to job constructor [OK]

Hint: Pass parameters inside dispatch() to send to job constructor [OK]

Common Mistakes:

• Trying to call dispatch on an instance
• Using dispatch as a function with wrong syntax
• Chaining with() method which does not exist