GoFuckYourself.com - Adult Webmaster Forum - View Single Post

sherlock.homme · 02-03-2015, 07:33 PM

The 20/20 usage of processes is definitely a bad thing. Like DonJon69 explained, it's the PHP processes instantiated by your server to serve incoming requests. Your server can have between 1 and 20 processes, what that means is that it can serve 20 concurrent users, which is plenty enough if your PHP layer is fast (depending on what you are doing that can allow you to support 50 to 100 requests per seconds, that's a lot of traffic).

The number of these you need depends of the server capacity and the application you run on it. But from experience, the number of processes allowed is rarely the actual problem, it's more often than not a symptom of something going wrong in your application.

You said you run custom code in there, I would advise you to profile it under load testing with XHProf (can't link sorry, not enough posts yet). It's a tool developed by Facebook to analyse PHP callstacks, it's extremely useful as if you have bottlenecks, you will have the exact spot in your code where it happens.

Another usual suspect when you have PHP processes hanging is the database. Have you checked that your database is responsive? If it's not done yet, turn on the slow query log for MySQL, and it will tell you if any query is taking an unusual amount of time to execute. Another place to look is the errors log of your server, if MySQL was faulting maybe it triggered a PHP error that was logged.

Focus on getting your PHP layer to be as fast as possible, that alone will allow you to grow to decent traffic sizes without having to do too much server optimization, on most distro the servers (Apache or Nginx) default settings are not that bad.

That being said, there are a lot of other things that could cause this, but in general this type of behaviour by your server will cause Google to penalize you as your error rate would be elevated as well as your response time and time to first byte. You might have had good content, which Google had identified, but were penalized heavily because your site was mostly not browsable, too slow, or throwing 502/503 (anyone reading, you should actively monitor the error rates on your server).

02-03-2015, 07:33 PM
sherlock.homme Registered User Industry Role: Join Date: Sep 2014 Location: UK Posts: 6	The 20/20 usage of processes is definitely a bad thing. Like DonJon69 explained, it's the PHP processes instantiated by your server to serve incoming requests. Your server can have between 1 and 20 processes, what that means is that it can serve 20 concurrent users, which is plenty enough if your PHP layer is fast (depending on what you are doing that can allow you to support 50 to 100 requests per seconds, that's a lot of traffic). The number of these you need depends of the server capacity and the application you run on it. But from experience, the number of processes allowed is rarely the actual problem, it's more often than not a symptom of something going wrong in your application. You said you run custom code in there, I would advise you to profile it under load testing with XHProf (can't link sorry, not enough posts yet). It's a tool developed by Facebook to analyse PHP callstacks, it's extremely useful as if you have bottlenecks, you will have the exact spot in your code where it happens. Another usual suspect when you have PHP processes hanging is the database. Have you checked that your database is responsive? If it's not done yet, turn on the slow query log for MySQL, and it will tell you if any query is taking an unusual amount of time to execute. Another place to look is the errors log of your server, if MySQL was faulting maybe it triggered a PHP error that was logged. Focus on getting your PHP layer to be as fast as possible, that alone will allow you to grow to decent traffic sizes without having to do too much server optimization, on most distro the servers (Apache or Nginx) default settings are not that bad. That being said, there are a lot of other things that could cause this, but in general this type of behaviour by your server will cause Google to penalize you as your error rate would be elevated as well as your response time and time to first byte. You might have had good content, which Google had identified, but were penalized heavily because your site was mostly not browsable, too slow, or throwing 502/503 (anyone reading, you should actively monitor the error rates on your server). __________________ ICQ: 699346918 Skype: KonradNettraffic Buying tubes, TGPs, MGPs & blogs. Small to medium sized. Contact at sherlock [dot] homme [dot] 86 [at] gmail [dot] com