FAQ Increase Performance: Difference between revisions

From Dolibarr ERP CRM Wiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
[[Category:FAQ EN]]
[[Category:FAQ EN]]
{{TemplateDocDev}}
{{TemplateDocUtil}}
Dolibarr is a web application designed to have best response time.
Dolibarr is a web application designed to have best response time.
A lot of technologies are used but some of them are not enabled by default as they need some specific skills to use them. This is a list of all possible things you can do to increase Dolibarr speed.
A lot of technologies are used but some of them are not enabled by default as they need some specific skills to use them. This is a list of all possible things you can do to increase Dolibarr speed.

Revision as of 22:27, 13 April 2011

Dolibarr is a web application designed to have best response time. A lot of technologies are used but some of them are not enabled by default as they need some specific skills to use them. This is a list of all possible things you can do to increase Dolibarr speed.


Recommanded solutions

Disable xdebug

Efficiency: *****

Principle: If php module xdebug is active, you should disable it. This module is a PHP feature to help developpers but it's useless for a production usage and slow down all PHP softwares. To know if this module is active, go on page Home-Setup-System info-PHP and do a search on xdebug. If you don't find anything, module is not active. If you find an occurence, module is active and can be disabled.. Enabling/Disabling such a module depends on your PHP system and OS. The most common way is to comment a line into you php.ini and restart web server.

Applicative cache using MemCached

Efficiency: *****

Principle: Installing a memcached server and the Module MemCached.

PHP OPCODE cache

Efficiency: ****

Principe: Install an apache/php module that save PHP pages compilation result into a cache. Each page access will be then faster. For this, you can install any PHP accelarator. xcache is one of the recommanded solution. Note that caching occurs here on a different level than Module MemCached, so gains are cumulative !

HTTP cache of static pages

Efficiency: ***

Principle: You can setup apache to activate explicit cache of static resources by adding following directives:

# Cache for static resources (Enable expiration and set it to A2592000 = 1 month)
ExpiresActive On
ExpiresByType image/x-icon A2592000
ExpiresByType image/gif A2592000
ExpiresByType image/png A2592000
ExpiresByType image/jpeg A2592000
ExpiresByType text/css A2592000
ExpiresByType text/javascript A2592000
ExpiresByType application/x-javascript A2592000
ExpiresByType application/javascript A2592000

Again, gain is cumulative with other previous caches.

Use mysqli driver instead of mysql

Efficiency: ***

Principle: If you use a mysql database, check into your Dolibarr config file htdocs/conf/conf.php that you have the line

$dolibarr_main_db_type='mysqli';

If value is mysql, change it into mysqli that provide better performances (gain is 30ms for each page call).

Search on beginning of field

Effciency: ***

Principle: If you activated, into Product module, the "autocomplete" search and list take a long time before to appear after typing a new character, this probably means you have an important number of product. Search is done everywhere in the text, so database index on field can't be used. By adding the constant PRODUCT_DONOTSEARCH_ANYWHERE to 1 into Home-Setup-Other, you limit the search to the beginning of strings making possible for database to use index and you should get an immediate response.

Use a recent web browser

Efficiency: ***

Principle: More and more features used Ajax or javascript technologies to offer a modern look and feel. Such technologies are an important part of time taken to show a page and are best processed with a recent web browser. Gap between a version and the next one are sometimes very important, so think to use an optimized web browser and always the last stable version (Firefox, Chrome, Safari or Opera). Avoid IE or other exotic web browsers.

Other solutions

Applicative cache using Shared memory

Efficiency: ****

Pre-requisites: Using an Apache web server

Principle: Add into Home-Setup-Other the constant MAIN_OPTIMIZE_SPEED. If value of constant has bit 1 set, Dolibarr will use shared memory to cache translation of language files. This means that only one language can be used (the one defined by first user that log after the Apache server reboot). Use instead of this option, the Module MemCached EN that has no limits and is more efficient.

Use precompressed version of Javascript libraries

Efficiency: *

Pre-requisites: Need to edit Apache setup.

Principle: Add into Home-Setup-Other the constant MAIN_OPTIMIZE_SPEED. If value of constant has bit 0 set, Dolibarr will use the minifying and compressed version of javascript. Apache server must be configured to have the line

AddType text/javascript .jgz
AddEncoding gzip .jgz

Then clean your cache browser. This feature seems to fails on HTTPS (security error for an unknown reason).

Compressing on the fly libraries and css

Efficiency: *

Principle: Add into Home-Setup-Other the constant MAIN_OPTIMIZE_SPEED. If value of constant has bit 2 defined (Example: MAIN_OPTIMIZE_SPEED=4), Dolibarr will return pages compressed into GZ (and if browser support it). This consume more CPU on server but reduce transfer time. Use it with slow connexion.


Note: To enable all optimization using MAIN_OPTIMIZE_SPEED, you must enable all bits (Example: MAIN_OPTIMIZE_SPEED=7 so 1+2+4 contains bit 0, 1 and 2).