This document discusses optimizing Laravel applications for production environments. It outlines several techniques for improving performance, including: 1. Using the artisan optimize command to dump autoloads and compile routes/configs. 2. Caching routes, configs, and objects to improve load times and reduce runtime compilation. 3. Chunking large database queries to improve memory usage. 4. Leveraging Laravel Mix to compile assets and reduce server requests. 5. Implementing service workers to enhance the progressive web app experience. When combined, these techniques allow Laravel applications to achieve omnipotent performance like Thanos and his infinity stones.

1. Optimizing
Laravel for
Production
Krisna Fathurahman
Co-Founder & Developer @ Mandala
Laravel.bdg meetup #2 (30/04/2018)

2. Have you ever build a
website?

3. Have you ever build for
hundreds? Thousands?
Or maybe, millions?

4. Do you believe in
performance?

5. Laravel application is like Infinity
Gauntlet...
“I now hold omnipotence. What should I
do with such almighty power? The
answer to that is actually quite simple:
‘Anything I want.’” - Thanos
When all infinity stones assembled,
when you knew how they work, you can
control the universe with a snap of
finger.

6. Let’s learn its
power
SPOILERS AHEAD!!!

7. Power by Default: Artisan Optimize
$ php artisan optimize
- Runs on composer post-install or post-update by default
- Dump generated autoload file & recompiled autoload file with PSR-0 & PSR-4
classmaps and packages
- Saved in bootstrap/cache/services.php & bootstrap/cache/packages.php

8. 1st Power: Route Cache
$ php artisan route:cache
- Forbid usage of closure function inside routes
- Turns RouteCollection class into base64 string. So, no need to compile web.php and
api.php on runtime (compiled ahead of time)
- Saved in bootstrap/cache/routes.php

9. 2nd Power: Config Cache
$ php artisan config:cache
- Forbid usage of env() function outside config directory (NO WARNING!!!). Use
config() function instead
- Compile all config files into single config file. So, no need to compile config/*.php
and parse .env on runtime (compiled ahead of time)
- Saved in bootstrap/cache/configs.php

10. 3rd Power: Database Chunking
LargeDataModel::where(‘name’, ‘like’, ‘%thanos%’)
->chunk(<number of rows>, <callback function for combining/projection etc.>)
- Save up your memory usage A LOT! Use it on large database query
- Chunking query builder into several database query. With the power of “offset”
syntax (assume we’re using MySQL)
- How many is “several”? several = ceiling(<num. of datarows>/<num. of rows>)
102,386 rows in database we’re chunking every 10,000, so it will run 11 queries

11. 4th Power: Object Caching
return Cache::remember(<cache key>, <num. of minutes>, function() {
// query goes here
});
- Reduce execution time for database query
- Automatically manage cached data with expiration time & cache key
- Cache key is application scoped. Be aware when defining cache key

12. 5th Power: Laravel Mix
- Compile all your assets into single file.
Reduce asset request to server
- Static cache friendly (because of
hashing)
- Using Webpack as its core. Customize
easily
- Min. Laravel v5.3.*

13. 6th Power: Service Worker
Enhance your user experience with Progressive Web Application!
Workbox (currently v3.*)
tl;dr: “service worker generator”
Compatible with webpack (Laravel Mix flow)
using additional webpack plugin

14. With all power
acquired,
performance wins
Thank you
/krsnadjava25