Home > Article > PHP Framework > How to optimize performance in Laravel8? Optimization Tips Sharing
This guide lists various performance optimization tips, from quick optimizations to in-depth tuning, that can help build high-performance Laravel applications.
There are many students on Enlightn who helped us write this guide. If you are looking for Laravel automation performance or security tools, you may wish to visit this website.
There is no doubt that users prefer faster apps to slower ones. .
According to a study by Google, 53% of users on mobile terminals will lose (choose to leave) if a website takes more than 3 seconds to load. And the average loading time for a mobile website is about 15 seconds. This is why performance matters!
Every additional second your app takes to load, the lower your customer conversion rate will be. Fortunately, for Laravel applications, this is not a difficult problem to solve.
Laravel has some built-in performance improvement features that can be used with a simple configuration.
The most critical performance improvement is Route cache. Did you know that every time your Laravel application is launched, the middleware is determined, aliases are resolved, route groups are resolved, route controller actions are specified, and request parameters are processed?
You can use the Artisan command route:cache
to cache all required routing information, thereby skipping route processing:
php artisan route:cache
This command can give you 5 times Performance improvements! It is the simplest and most effective optimization.
In addition to route caching, Laravel also provides the following:
.env
and config
Parsing of files. Tip: You should make sure to add the above cache command to your deployment script so that it is re-cached every time you deploy. Otherwise, any changes to routing or configuration files will not be reflected in the app.
A common mistake made by Laravel developers is to install all dependencies in production mode. Some development packages, such as Ignition, record queries, logs, and dumps in memory, providing friendly error messages with context and simplifying debugging. While this is useful in development, it can slow down your application in production.
In the deployment script, when using Composer to install the expansion package, be sure to use the -no-dev
option:
composer install --prefer-dist --no-dev -o
In addition, please ensure that in the production environment as mentioned above Use the -o
option. This allows Composer to optimize the autoloader by generating "classmaps".
If your application does not generate classes at runtime, you may choose to use the --classmap-authoritative
option instead of the -o
option for further optimization. Be sure to check out the Autoloader's Composer documentationOptimization strategies.
Choose the right driver Caches, queues, and session drivers can have a huge impact on application performance.
For caching in production environments, memory cache drivers such as Redis, Memcached or DynamoDB are recommended. You might consider using local filesystem caching for a single-server setup, although this will be slower than the cache-to-memory option.
For queues, it is recommended to use the Redis, SQS or Beanstalkd driver. The database queue driver is not suitable for production environments and is known to have deadlock issues.
For Session, database, Redis, Memcached or DynamoDB driver is recommended. The cookie driver has file size and security restrictions and is not recommended for production environments.
In a typical web request process, there may be some specific tasks that require a lot of time. It takes a long time to complete. Laravel has a first-class queue system, which allows us to transfer time-consuming tasks to queued tasks, allowing your application to respond to requests extremely quickly. In general, common examples of such tasks include parsing and storing CSV files, interacting with third-party APIs, sending notifications to users, long and time-consuming database queries, and search index updates. Compression headers can have a significant impact on application performance. Make sure you enable compression or CDN on your web server for text format files such as CSS, JS, XML, or JSON. Image formats already have compression algorithms implemented and in most cases image format files have been compressed, and images are not text format files (except for SVG format, which is an XML document). Therefore, the image format does not require compression. You can set up gzip or brotli (older browsers may not support brotli) on your web server or CDN to get a big performance boost. Normally, compression can reduce file size by about 80%! Caching can improve the performance of your application, especially for static resources, such as Images, CSS and JS files. It is recommended to enable cache control headers at the web server or CDN level, if applicable. If you wish to set these control headers on the Larvel application instead of the WebServer, you can use Larvel's Cache Control Middleware. The Cache header field ensures that the browser does not repeatedly request static resources when visiting the website multiple times. This improves the user experience as the website loads faster on subsequent visits. Laravel Mix provides cache cleaning functionality out of the box so that when CSS or JS code is changed, the browser does not continue to use old cached content. A content delivery network (CDN) is a geographically distributed server group that uses Servers closer to website visitors are provided. This allows users to experience faster loading times. In addition to faster loading speeds and shorter loading times, CDN also has other advantages, such as reducing web server load, DDOS protection and analysis of static resource services, etc. Some popular CDNs include CloudFlare, AWS CloudFront, and Azure CDN. Most CDNs have a certain free trial limit. Consider using a CDN to improve static resource loading performance. Laravel provides out-of-the-box CDN support components Mix and helper functions asset in the framework. Minimizing scripts will remove unnecessary overhead from your application Code (such as code comments, whitespace, shortened variable names, and other optimizations). This is a common and effective way to reduce the size of JS and CSS files in production environments. Laravel Mix provides out-of-the-box minimize output functionality for your production scripts Laravel has built-in caching support. Caching is best used for read-heavy workloads. These workloads often involve time-consuming data retrieval or data processing tasks. Some common scenarios for caching may include: Keep in mind that caching is not useful for You must also ensure that the cache is invalidated or flushed every time the cached content changes. For example, if you are caching profile headers, refresh the cache after a user updates their profile picture. If some of your pages take longer to load or have higher memory usage , you may need to identify performance bottlenecks. There are many tools in the Laravel ecosystem to help you do this, including Laravel Telescope, Laravel Debugbar, and Clockwork. Some common performance bottlenecks include: If you are unable to identify performance bottlenecks in your application using the above debugging tools, you may consider using analysis tools such as XDebug or Blackfire. In addition, here is a complete online checklist for reference41. Course Summary|《LX3 Laravel Performance Getting Started with Optimization》. Performance optimization is an eternal topic, but Laravel has several built-in components such as Mix, queues and cache, which makes Performance optimization looks easy! We hope you learned something new about improving application performance. Original address: https://laravel-news.com/performance-checklist Translation address: https://learnku.com/laravel/t/55702 [Related recommendations: laravel video tutorial]
5. Text file settings HTTP compression headers
6. Set HTTP cache headers on static resources
7. Use CDN services to accelerate static resources
8. Minimize JS and CSS code
9. Use cache wisely
long tail
(items that are rarely requested). On the contrary, it should be used with caution for any frequent data retrieval (as compared to data updates).
10. Identify your application’s performance bottlenecks
Online Checklist
Summary
The above is the detailed content of How to optimize performance in Laravel8? Optimization Tips Sharing. For more information, please follow other related articles on the PHP Chinese website!