1) PHP is Rarely The Bottleneck: http://talks.php.net/show/drupal08/<http://talks.php.net/show/drupal08/7> 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 scalability, ditch apache and use a better webserver 5) You're describing what ajax does in a lot of cases 6) Have you deployed flatfile cache / apc / memcached? If so, how? 7) Do you regularly run siege tests on new server stacks and profile each piece's impact on performance? 8) Do you profile your code every time you change some piece of logic?
Scalability is an enormous mountain to climb and there's only so much you can offload on to the client. Chances are there's more room for improvement at any stage in your development than there is potentiality for client-side processing. On Tue, May 26, 2009 at 10:46 PM, tRace DOliveira <married...@yahoo.com>wrote: > 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 could be done for PHP also. > Thank you, > Leonard D'Oliveira > > >
