Customer site access slow analysis and troubleshooting process

Recently I maintained a customer site is very slow to open, so they follow the previous troubleshooting steps to troubleshoot

1, log on to the server top command to view load IO condition discovery Load is a bit high and there are many PHP processes that make up a lot of resources

2, access the MySQL server to view the database thread, and did not find the lock table condition.

3, open the Web Access log found a lot of Baidu crawler visit. Causing a lot of PHP resources to be ordered

Solution:

1, disable crawler (not conducive to SEO)

Add in nginx config file

if ($http _user_agent ~ baiduspider) {return 503;}
if ($http _user_agent ~ etaospider) {return 503;}
if ($http _user_agent ~ Googlebot) {return 503;}
if ($http _user_agent ~ "Bingbot") {return 503;}

It is said that return 503 is based on SEO considerations

2, through Nginx to determine whether it is Baidu Crawler if it is to access the cache

Seoul Mall
Costume collocation
City of words and things
Dressing and blogging

Costume collocation Blog

Customer site access slow analysis and troubleshooting process