Filesystem configuration in Laravel - Performance & Optimization

Performance: Filesystem configuration

MEDIUM IMPACT

This affects how quickly your application can read and write files, impacting page load speed and response time when accessing storage.

Configuring file storage for user uploads

Laravel

FILESYSTEM_DRIVER=s3

// Using cloud storage (S3) with async upload and caching for media files

Offloads file storage to a remote service, reducing server load and enabling faster response times.

📈 Performance Gainnon-blocking file operations, reduces server CPU and I/O usage

Configuring file storage for user uploads

Laravel

FILESYSTEM_DRIVER=local

// Using local disk for all file storage including large media files

Local disk access can block requests if many large files are read or written synchronously, slowing response time.

📉 Performance Costblocks rendering for 50-200ms on large file operations

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Local disk synchronous file access	N/A	N/A	Blocks server response delaying paint	[X] Bad
Cloud storage with async upload and caching	N/A	N/A	Faster server response enables quicker paint	[OK] Good

Rendering Pipeline

Filesystem configuration affects the server response time before the browser starts rendering. Slow file reads delay HTML delivery, impacting the critical rendering path.

→Server Processing

→Network Transfer

→First Paint

⚠️ BottleneckServer Processing (file I/O delays)

Core Web Vital Affected

LCP

This affects how quickly your application can read and write files, impacting page load speed and response time when accessing storage.

Optimization Tips

1Avoid synchronous local disk file operations during request handling.

2Use asynchronous or queued file uploads to prevent blocking.

3Leverage remote storage with caching to speed up file access.

Performance Quiz - 3 Questions

How does using local disk synchronous file storage affect page load?

A It can block server response, delaying page rendering.

B It speeds up page rendering by caching files in memory.

C It has no impact on page load speed.

D It reduces network latency for users.

DevTools: Network

How to check: Open DevTools > Network tab, reload the page, and observe the Time to First Byte (TTFB) and resource loading times.

What to look for: High TTFB or long delays before HTML starts loading indicate slow server file operations.

Practice

1. What is the purpose of the default key in Laravel's config/filesystems.php file?

easy

A. It sets the default storage disk Laravel uses for file operations.

B. It defines the maximum file size allowed for uploads.

C. It specifies the encryption method for stored files.

D. It lists all available storage disks in the application.

Solution

1. Step 1: Understand the role of the default key

   The default key in config/filesystems.php tells Laravel which disk to use when no specific disk is mentioned.

2. Step 2: Compare with other options

   Options A, B, and C describe unrelated settings. Only "It sets the default storage disk Laravel uses for file operations." correctly describes the default disk setting.

3. Final Answer:

   It sets the default storage disk Laravel uses for file operations. -> Option A

4. Quick Check:

   Default disk = storage location [OK]

Hint: Default disk means where files go if no disk specified [OK]

Common Mistakes:

• Confusing default disk with file size limits
• Thinking default sets encryption
• Assuming default lists all disks

2. Which of the following is the correct syntax to define a local disk in config/filesystems.php?

easy

A. 'local' => ['driver' => 'ftp', 'root' => storage_path('app')],

B. 'local' => ['driver' => 'local', 'root' => storage_path('app')],

C. 'local' => ['driver' => 's3', 'root' => storage_path('app')],

D. 'local' => ['driver' => 'local', 'root' => public_path('app')],

Solution

1. Step 1: Identify the correct driver for local disk

   The local disk uses the 'local' driver, so options with 'ftp' or 's3' are incorrect.

2. Step 2: Check the root path for local storage

   The root path for local disk is usually storage_path('app'), not public_path('app').

3. Final Answer:

   'local' => ['driver' => 'local', 'root' => storage_path('app')], -> Option B

4. Quick Check:

   Local driver + storage_path = correct syntax [OK]

Hint: Local disk uses 'local' driver and storage_path root [OK]

Common Mistakes:

• Using wrong driver like 'ftp' or 's3' for local disk
• Setting root to public_path instead of storage_path
• Mixing driver and root paths

3. Given this config/filesystems.php snippet:

'disks' => [
    's3' => [
        'driver' => 's3',
        'key' => env('AWS_ACCESS_KEY_ID'),
        'secret' => env('AWS_SECRET_ACCESS_KEY'),
        'region' => env('AWS_DEFAULT_REGION'),
        'bucket' => env('AWS_BUCKET'),
    ],
],
'default' => 's3',

What happens when you call Storage::put('file.txt', 'Hello') in your app?

medium

A. An error occurs because the local disk is not set.

B. The file is saved to the local storage folder.

C. The file is saved to the configured Amazon S3 bucket.

D. The file is saved to a temporary directory.

Solution

1. Step 1: Identify the default disk

   The default disk is set to 's3', so all Storage calls use the S3 disk unless specified otherwise.

2. Step 2: Understand Storage::put behavior

   Calling Storage::put saves the file to the default disk, which is the S3 bucket configured.

3. Final Answer:

   The file is saved to the configured Amazon S3 bucket. -> Option C

4. Quick Check:

   Default disk 's3' means files go to S3 [OK]

Hint: Default disk controls Storage::put location [OK]

Common Mistakes:

• Assuming file saves locally despite default 's3'
• Thinking missing local disk causes error
• Confusing temporary directory with storage

4. You added a new disk in config/filesystems.php but get an error when using it. Which of these is the most likely cause?

medium

A. You forgot to run php artisan config:cache after changing the config.

B. You used the wrong PHP version for Laravel.

C. You did not install the Laravel UI package.

D. You set the disk name to 'default' instead of a unique name.

Solution

1. Step 1: Understand Laravel config caching

   Laravel caches config files for performance. Changes in config files require clearing or caching again.

2. Step 2: Identify the common fix

   Running php artisan config:cache refreshes the cached config and applies new disk settings.

3. Final Answer:

   You forgot to run php artisan config:cache after changing the config. -> Option A

4. Quick Check:

   Config cache must refresh after edits [OK]

Hint: Run config:cache after config changes [OK]

Common Mistakes:

• Ignoring config cache after edits
• Blaming PHP version for config errors
• Confusing unrelated packages with filesystem config

5. You want to configure a new disk in config/filesystems.php that stores files on a remote FTP server. Which of these is the correct minimal configuration?

hard

A. 'ftp' => [ 'driver' => 's3', 'key' => env('FTP_KEY'), 'secret' => env('FTP_SECRET') ],

B. 'ftp' => [ 'driver' => 'local', 'root' => env('FTP_HOST') ],

C. 'ftp' => [ 'driver' => 'ftp', 'bucket' => env('FTP_BUCKET') ],

D. 'ftp' => [ 'driver' => 'ftp', 'host' => env('FTP_HOST'), 'username' => env('FTP_USERNAME'), 'password' => env('FTP_PASSWORD') ],

Solution

1. Step 1: Identify the correct driver for FTP

   The driver must be 'ftp' to connect to an FTP server, so options with 'local' or 's3' are incorrect.

2. Step 2: Check required connection details

   FTP requires host, username, and password. 'ftp' => [ 'driver' => 'ftp', 'host' => env('FTP_HOST'), 'username' => env('FTP_USERNAME'), 'password' => env('FTP_PASSWORD') ], includes these minimal required keys.

3. Final Answer:

   'ftp' => [ 'driver' => 'ftp', 'host' => env('FTP_HOST'), 'username' => env('FTP_USERNAME'), 'password' => env('FTP_PASSWORD') ], -> Option D

4. Quick Check:

   FTP driver + host, username, password needed [OK]

Hint: FTP disk needs driver 'ftp' and host, user, password [OK]

Common Mistakes:

• Using wrong driver like 'local' or 's3' for FTP
• Missing required host or credentials
• Confusing bucket with FTP config