Re: [PHP-DEV] PHP scalability problem

nginx and php-fpm is the fastest setup I could find, after spending almost 2 weeks trying different combinations. Apache pre-fork model: 1900 reqs/second (this is with running queries per pageload) nginx w/ fpm: 3400 reqs/second And nginx's doc setup is awesome. Like Michael said, scaling PHP it

Re: [PHP-DEV] PHP scalability problem

Succinct and great reply. Better webserver: nginx :) #3 is probably the most important piece. I'd like to also note scaling php is pretty simple. Scaling out typically provides better results as opposed to scaling up. Scaling your datastore will always be your pain point. Adding new data no

Re: [PHP-DEV] PHP scalability problem

On 26-May-09, at 11:10 PM, tRace DOliveira wrote: What I am trying to achieve is to have the server do less processing. Like I said PHP is a server side scripting language and each time a request is made a process is spawned and processes are heavy weight as compared to a thread which is a

[PHP-DEV] PHP scalability problem

What I am trying to achieve is to have the server do less processing. Like I said PHP is a server side scripting language and each time a request is made a process is spawned and processes are heavy weight as compared to a thread which is a light weight process. So I want to take away much proce

Re: [PHP-DEV] PHP scalability problem

1) PHP is Rarely The Bottleneck: http://talks.php.net/show/drupal08/ 2) Invest in an opcode cache 3) DB I/O is always the most restrictive part of your application, read the mysql performance blog (a lot applies for postgres too) 4) If you're serious about scal

[PHP-DEV] PHP scalability problem

PHP is a server side scripting language, so that means that the server will have to do the bulk of the processing if not most. I was thinking about shifting the processing to the client. Kinda like how java does it. I don't know really know how java does it but it would be interesting if it cou