{"id":73,"date":"2012-08-15T15:52:00","date_gmt":"2012-08-15T15:52:00","guid":{"rendered":"https:\/\/www.tech-and-dev.com\/blog\/2012\/08\/15\/how-to-install-eaccelerator-on-linux\/"},"modified":"2021-02-22T00:59:39","modified_gmt":"2021-02-22T00:59:39","slug":"how-to-install-eaccelerator-on-linux","status":"publish","type":"post","link":"https:\/\/www.tech-and-dev.com\/blog\/2012\/08\/how-to-install-eaccelerator-on-linux.html","title":{"rendered":"How to install eAccelerator on linux"},"content":{"rendered":"

\"php<\/a><\/p>\n

\u00a0eAccelerator works in a way that whenever there is request to a webpage, eAccelerator will parse all the php files and cache them in a shared memory in their compiled state. This way, anytime a request is made, eAccelerator will serve those compiled files from the memory, and thus will almost eliminate the entire parsing process.<\/div>\n
<\/div>\n
eAccelerator is a very useful extension to reduce the CPU overloads, serve the requests faster, and optimize the php performance.<\/div>\n
According to php eAccelerator official website, eAccelerator can speed up the php code by 1-10 times and reduce server load.<\/div>\n
<\/div>\n
Installing eaccelerator is an easy process, just follow the below steps to install your eaccelerator on\u00a0 linux.<\/div>\n
In this tutorial, I will be installing eAccelerator on a CentOS.<\/div>\n
<\/div>\n
First, make sure you have the php extension php-devel<\/i> installed, you can install it using yum (More about linux commands here<\/a>):<\/div>\n
yum install php-devel<\/div>\n

Now let’s download eAccelerator to a temporary directory<\/p>\n

cd \/tmp
\nwget http:\/\/acelnmp.googlecode.com\/files\/eaccelerator-0.9.6.1.tar.bz2<\/div>\n

Extract it:<\/p>\n

tar xvfj eaccelerator-0.9.6.1.tar.bz2<\/div>\n

Change the directory to eAccelerator dir:<\/p>\n

cd eaccelerator-0.9.6.1<\/div>\n

Now let’s use PHPize to prepare a PHP extension for compiling:<\/p>\n

phpize
\n.\/configure<\/div>\n

Let’s install eAccelerator:<\/p>\n

make
\nmake install<\/div>\n

eAccelerator should now be installed.
\nLet’s tell php to read it and start caching:
\nIn this step, we can either create a separate file for the eaccelerator configuration or we can append them to php.ini, I will use the first method in this example.
\nWe create the eaccelerator ini file:<\/p>\n

vi \/etc\/php.d\/eaccelerator.ini<\/div>\n

and we write the following<\/p>\n

extension=”eaccelerator.so”
\neaccelerator.shm_size=”64″
\neaccelerator.cache_dir=”\/var\/cache\/eaccelerator”
\neaccelerator.enable=”1″
\neaccelerator.optimizer=”1″
\neaccelerator.check_mtime=”1″
\neaccelerator.debug=”0″
\neaccelerator.filter=””
\neaccelerator.shm_max=”0″
\neaccelerator.shm_ttl=”0″
\neaccelerator.shm_prune_period=”0″
\neaccelerator.shm_only=”0″
\neaccelerator.compress=”1″
\neaccelerator.compress_level=”9″<\/div>\n

In the above example, I’m allowing eAccelerator to allocate up 64MB in memory. If you want to allow it to allocate less or more, change the value of eaccelerator.shm_size<\/b>, setting it to 0 will use the default value.<\/p>\n

Now we need to define a directory to be used for eAccelerator caching.
\nLet’s create a new directory:<\/p>\n

mkdir -p \/var\/cache\/eaccelerator<\/div>\n

and change permissions to read, write and execute:<\/p>\n

chmod 0777 \/var\/cache\/eaccelerator<\/div>\n

Now let’s restart apache:<\/p>\n

service httpd restart<\/div>\n

or<\/p>\n

\/etc\/init.d\/httpd restart<\/div>\n

Congratulations, you now have eAccelerator installed. You can check in your phpinfo() for the eaccelerator section.<\/p>\n

\"\"<\/p>\n

If you are unable to restart Apache server, and you receive an error, make sure your server allows you to allocate enough memory. Check this article for more details: Increase shared memory on linux (shmmax)<\/a><\/p>\n

Follow us on facebook<\/a> or twitter<\/a> for the latest updates!<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

\u00a0eAccelerator works in a way that whenever there is request to a webpage, eAccelerator will parse all the php files and cache them in a shared memory in their compiled state. This way, anytime a request is made, eAccelerator will serve those compiled files from the memory, and thus will almost eliminate the entire parsing […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[97,6,96,22,7],"tags":[],"class_list":["post-73","post","type-post","status-publish","format-standard","hentry","category-eaccelerator","category-linux","category-performance","category-php","category-ssh"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.tech-and-dev.com\/blog\/wp-json\/wp\/v2\/posts\/73","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.tech-and-dev.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tech-and-dev.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tech-and-dev.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tech-and-dev.com\/blog\/wp-json\/wp\/v2\/comments?post=73"}],"version-history":[{"count":1,"href":"https:\/\/www.tech-and-dev.com\/blog\/wp-json\/wp\/v2\/posts\/73\/revisions"}],"predecessor-version":[{"id":188,"href":"https:\/\/www.tech-and-dev.com\/blog\/wp-json\/wp\/v2\/posts\/73\/revisions\/188"}],"wp:attachment":[{"href":"https:\/\/www.tech-and-dev.com\/blog\/wp-json\/wp\/v2\/media?parent=73"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tech-and-dev.com\/blog\/wp-json\/wp\/v2\/categories?post=73"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tech-and-dev.com\/blog\/wp-json\/wp\/v2\/tags?post=73"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}