background preloader

eAccelerator

APC (PHP Accelerator) Disclaimer: i do not guarantee it will work for you so you better use it at your own risk. It works for me. * I am using # symbol for all shell commands I am posting a quick step-by-step guide to install APC on servers (dedicated or VPS) with cpanel/whm working. First login as a root to your server/vps and make a directory to work with this plugin, #mkdir /home/APC-php #cd /home/APC-php now here we will first download the APC with following command #wget you can check for the latest version now you can use gzip and tar separately or tar -xzvf to unzip this file #tar -xzvf APC-3.0.14.tgz now you will have a APC-3.0.14 folder. #cd APC-3.0.14 now you have to make php configuration files by following command #phpize after this use following three commands # . #make #make test #make install NOTE: if you are using suPHP then skip --with-apxs *one more thing, if you use check your php.ini location by #php -i | grep php.ini then open it with your favorite editor. mine was at

eAccelerator Not to be confused with the computer security company eAcceleration. Every time a PHP script is accessed, PHP usually parses and compiles scripts to bytecode. Once installed, eAccelerator optimizes the compiled bytecode and caches this to shared memory or disk or both. Upon subsequent accesses to a script, eAccelerator will access cached bytecode if it is available instead of the script being compiled. This avoids the performance overhead of repeated parsing and compilation. Previous eAccelerator versions also provided functions[1] for use in PHP scripts that allow access to shared memory, automatic web (content) caching, and other related tasks. Old eAccelerator versions had an encoder component that creates a file that cannot be as easily read as a normal PHP script, offering some code protection. EAccelerator is free software released under the GNU GPL 2.0. See also[edit] References[edit] External links[edit]

PHP Home · eaccelerator/eaccelerator Wiki BD (MYSQL) Servidor WEB (Apache) Lighttpd - fly light MYISAM or InnoDB Innodb Performance Optimization Basics November 1, 2007 by Peter Zaitsev77 Comments Note: There is an updated post on this topic here. Interviewing people for our Job Openings I like to ask them a basic question – if you have a server with 16GB of RAM which will be dedicated for MySQL with large Innodb database using typical Web workload what settings you would adjust and interestingly enough most people fail to come up with anything reasonable. Hardware If you have large Innodb database size Memory is paramount. 16G-32G is the cost efficient value these days. Operating System First – run 64bit operating system. MySQL Innodb Settings The most important ones are: innodb_buffer_pool_size 70-80% of memory is a safe bet. Also check if your application can run in READ-COMMITED isolation mode – if it does – set it to be default as transaction-isolation=READ-COMMITTED. There are bunch of other options you may want to tune but lets focus only on Innodb ones today.

Related: