Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>A wild guess might be that JAVA depends on some kind of "application" server, while PHP doesn't -- which means a new environnement has to be created each time a PHP page is called.</p> <p><em>(This was especially true when PHP was/is used as a CGI, and not as an Apache module or via FastCGI)</em></p> <p><br> Another idea might be that C# and JAVA compilers can do some heavy optimisations at compile time -- on the other side, as PHP scripts are compiled <em>(at least, if you don't "cheat" with an opcode cache)</em> each time a page is called, the compilation phase has to be real quick ; which means it's not possible to spend much time optimizing.</p> <p><br> Still : Each version of PHP generally comes with some amelioration of the performances ; for instance, you can gain between 15% and 25% of CPU, when switching from PHP 5.2 to 5.3.</p> <p>For instance, take a look at those benchmarks :</p> <ul> <li><a href="http://sebastian-bergmann.de/archives/745-Benchmark-of-PHP-Branches-3.0-through-5.3-CVS.html" rel="nofollow noreferrer">Benchmark of PHP Branches 3.0 through 5.3-CVS</a></li> <li><a href="http://ez.no/developer/forum/developer/performance_php_5_2_vs_php_5_3_huge_gain" rel="nofollow noreferrer">Performance PHP 5.2 vs PHP 5.3 - huge gain</a></li> <li><a href="http://blog.pascal-martin.fr/post/bench-php-5.2-vs-php-5.3-cpu" rel="nofollow noreferrer">Bench PHP 5.2 vs PHP 5.3</a> <em>-- disclaimer : it's in french, and I'm the one who did it.</em></li> </ul> <p><br> One important thing, also, is that PHP is quite easy to scale : just add a couple of web servers, and voila !</p> <p>The problem you often meet when going from 1 to several servers is with sessions -- store those in DB or memcached <em>(very easy)</em>, and problem solved !</p> <p><br> As a sidenote : I would not recommend choosing a technology because there is a couple of percent difference of speed on some benchmark : there are far more important factors, like how well your team know each technology -- or, even, the algorithms you are going to use !</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload