Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Unless you actually have a performance problem that can be directly attributed to PHP's performance, then I'd strongly advise avoiding HipHop. It can certainly (if used properly) handle extremely high traffic, but it also isn't fully compatible with PHP. As has already been stated, not all PHP extensions work with HipHop. </p> <p>If you are having performance issues, then there are other alternatives you can look at before having to resort to HipHop. First, review the performance of your scripts, determine the bottlenecks and optimize them. This is the part of the application you have the most control over and therefore the place where you should start. Interaction with external resources, especially databases and remote servers, are a good starting point as this is where operations tend to have the most time-expense. Database performance can be improved by reducing the query load and wise choice of indexes for the tables (Hint, ORM tends to produce very sub-optimal query patterns). You can also offload especially expensive operations to cron-jobs to be run offline and have the online script just queue the operation. </p> <p>If this doesn't provide enough of a performance boost, then there's APC which caches PHP code in a "byte code" (for want of a better term) that doesn't have to be parsed before it can be run by the Zend Engine. This provides a performance boost. There are also other things you can do such as caching with memcache, caching results and so on to gain further performance boosts. </p> <p>If you still haven't gotten enough performance, then, and only then, should you consider HipHop. You should consider it a last resort, not a first resort. You also shouldn't start to worry about optimizing a project until such time as it's demonstrably suffering from performance issues. </p> <p>Never do premature optimization. </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.
    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