Record the experience of using Laravel-s to resist Baidu crawlers
The following tutorial column will record the experience of using Laravel-s to resist Baidu crawlers. I hope it will be helpful to friends in need!
LaravelS is a glue project for fast Integrate Swoole into Laravel or Lumen to give them better performance
github addressWhy use Laravel-s
After the Baidu applet was launched, the high qps (concurrency) of the Baidu crawler caused the CPU to be fully loaded and the server to crash. The server was configured with 4 cores, 8G memory and 5M broadband. What to do at this time?
Adjust the php-fpm parameters and set it to static. Static mode has higher performance than dynamic mode. For example, if you set the number of child processes to 255 or even higher, the higher the number, the greater the amount of concurrency it will bear, but the higher the number, the more memory it will occupy. Conclusion, it is effective to a certain extent, but it is useless under high concurrency.
Feedback to Baidu to adjust the crawler crawling frequency. Conclusion, wait a minute, the day lilies are already cold, but it’s better to give feedback.
Load balancing. Let other servers share the pressure. The premise is that there are enough servers and the same code must be deployed, and the business that other servers are originally responsible for cannot be affected. Or temporarily apply for N servers in a certain cloud, but you don’t know when the crawler will come and when it will go, which is unrealistic.
The next step is the topic of the article, using Laravel-s to accelerate http response.
Because there was no statistics for all periods at that timeqps Specific values, so there is no way to draw accurate conclusions. We can only compare based on the machine load before and after adjustment.
Before deployment, cpu
was fully loaded, and the machine was down N times and was paralyzed. The external network broadband is full (5M). After deployment, the cpu immediately drops to
. After temporarily upgrading the broadband to 15M, cpu
reaches 60%
. The external network broadband It is still fully occupied (it can only be said that Baidu crawler is a real one, you can get as much bandwidth as you want). In conclusion, it brings at least 5 times performance improvement.
The page crawled by the crawler is only part of the page, so the online project is not transformed into laravel-s is also unrealistic. We only need to separate the crawled pages and deploy them to
laravel-s separately. Create a new empty project, the business logic only processes the captured pages
- , the project port number is such as 6501
deployment laravel-s, test api and ab stress test
-
The online project will proxy the page path crawled by the crawler to the new project, such as
127.0.0.1:6501
A few points to note:<div class="code" style="position:relative; padding:0px; margin:0px;"><pre class='brush:php;toolbar:false;'>location ~ ^/v1/test.* { proxy_pass http://127.0.0.1:6501; proxy_set_header Host $host;}</pre><div class="contentsignin">Copy after login</div></div>
In
conf/laravels.php- , the default The number of
- worker
enabled is twice the number of
laravlescpu
cores. is running in - swoole
, in memory. Every time you change the code, you need to restart
laravellaravel-s
.Due to the reason in Article 2, the database connection cannot be released, and
needs to be enabled to disconnect and reconnect (>laravle5.1). Add <div class="code" style="position:relative; padding:0px; margin:0px;"><pre class='brush:php;toolbar:false;'>&#39;options&#39; => [ // 开启持久连接 \PDO::ATTR_PERSISTENT => true,],</pre><div class="contentsignin">Copy after login</div></div> in
conf/database.phpconfiguration
The above is the detailed content of Record the experience of using Laravel-s to resist Baidu crawlers. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The latest versions of Laravel 9 and CodeIgniter 4 provide updated features and improvements. Laravel9 adopts MVC architecture and provides functions such as database migration, authentication and template engine. CodeIgniter4 uses HMVC architecture to provide routing, ORM and caching. In terms of performance, Laravel9's service provider-based design pattern and CodeIgniter4's lightweight framework give it excellent performance. In practical applications, Laravel9 is suitable for complex projects that require flexibility and powerful functions, while CodeIgniter4 is suitable for rapid development and small applications.

Compare the data processing capabilities of Laravel and CodeIgniter: ORM: Laravel uses EloquentORM, which provides class-object relational mapping, while CodeIgniter uses ActiveRecord to represent the database model as a subclass of PHP classes. Query builder: Laravel has a flexible chained query API, while CodeIgniter’s query builder is simpler and array-based. Data validation: Laravel provides a Validator class that supports custom validation rules, while CodeIgniter has less built-in validation functions and requires manual coding of custom rules. Practical case: User registration example shows Lar

For beginners, CodeIgniter has a gentler learning curve and fewer features, but covers basic needs. Laravel offers a wider feature set but has a slightly steeper learning curve. In terms of performance, both Laravel and CodeIgniter perform well. Laravel has more extensive documentation and active community support, while CodeIgniter is simpler, lightweight, and has strong security features. In the practical case of building a blogging application, Laravel's EloquentORM simplifies data manipulation, while CodeIgniter requires more manual configuration.

Laravel - Artisan Commands - Laravel 5.7 comes with new way of treating and testing new commands. It includes a new feature of testing artisan commands and the demonstration is mentioned below ?

When choosing a framework for large projects, Laravel and CodeIgniter each have their own advantages. Laravel is designed for enterprise-level applications, offering modular design, dependency injection, and a powerful feature set. CodeIgniter is a lightweight framework more suitable for small to medium-sized projects, emphasizing speed and ease of use. For large projects with complex requirements and a large number of users, Laravel's power and scalability are more suitable. For simple projects or situations with limited resources, CodeIgniter's lightweight and rapid development capabilities are more ideal.

Microservice architecture uses PHP frameworks (such as Symfony and Laravel) to implement microservices and follows RESTful principles and standard data formats to design APIs. Microservices communicate via message queues, HTTP requests, or gRPC, and use tools such as Prometheus and ELKStack for monitoring and troubleshooting.

For small projects, Laravel is suitable for larger projects that require strong functionality and security. CodeIgniter is suitable for very small projects that require lightweight and ease of use.

Comparing Laravel's Blade and CodeIgniter's Twig template engine, choose based on project needs and personal preferences: Blade is based on MVC syntax, which encourages good code organization and template inheritance. Twig is a third-party library that provides flexible syntax, powerful filters, extended support, and security sandboxing.
