How can I optimize LiveZilla's performance?
LiveZilla is designed to process a huge amount of real-time information and it will always consume a certain amount of CPU time and server resources for technical reasons.
Generally speaking, the more
(operators, website visitors, chats) you have the more information needs to be processed (=higher CPU load) and downloaded by the clients (=higher bandwidth).
Another crucial factor is the
in which the clients will ask the server for updates. The more often clients ask the server for updates, the faster information will reach its destination. However: The more often clients ask the server for updates, the higher the server load (CPU time, resources, bandwidth).
How to optimize the performance?
Change mySQL Engine (Effect:
Moderate) Convert your MySQL tables engine from MyISAM to InnoDB if supported. InnoDB turned out to provide a better overall performance for LiveZilla. Deactivate Statistics (Effect:
Significant) Deactivate statistics to store and process less data. Server Configuration -> Statistics. Activate Shared Memory Caching (Effect:
Moderate) From version 5.2.x LiveZilla makes use of PHP's in-built shared memory / caching functions (Memcached,Memcache,SHMOP,APC,MySQL) to reduce the amount of MySQL queries significantly. Please make sure shared memory caching is activated under Server Configuration -> Server. If you don't know what caching engine to choose, please go for "MySQL". Increase connection frequencies (Effect:
Significant) You can change the amount of connections per client (visitor, operator, chat) through the configuration. Under Server Configuration -> Server you will find two settings, the visitor poll frequency and the client poll frequency. These values determine the frequency of connections between client and server side. The visitor poll frequency affects the real-time visitor monitoring while the client poll frequency affects operator clients and the customer side chat window (=chats). The lower the value, the more often will the client/browser connect to the server. If you double both values you will halve the amount of connections. Reduce visitor history data (Effect:
Significant) By default, LiveZilla will keep real-time visitor monitoring information for the past three days. Depending on the amount of visitors you have on your website, this can result a larger tables and slower MySQL queries. You can decrease the number of days under: Server Configuration -> Visitor Monitoring -> Delete history. Deactivate Visitor Monitoring (Effect:
High) Do you actually need visitor monitoring? If you are using LiveZilla mainly for chats and if you have lots of visitors on your website, please consider to deactivate visitor monitoring under Server Configuration -> Visitor Monitoring. Remove Idle Operators (Effect: Significant) Please note that operators consume the greatest amount of resources from all objects (by far). Please consider to log off operators that do not actively work in the system.
If your webhosting company tells you that LiveZilla causes Shared Hosting Problems unusual high load affecting the server stability, please keep in mind what shared hosting means: numerous companies put their web sites on the same physical server. That means you have neighbours and whatever you do will potentially affect all of them. It (most likely) also means, that you enjoy incredibly low rates. As a webhosting company, you have many competitors these days and you are required to keep prices very low in order to be competitive. All hosting companies will try to put as many clients on each server as possible to generate an acceptable revenue. That reduces tolerances and clients are usually expected to run a small website but nothing else on-top. Especially frequent connections (like they are typical for chat and monitoring applications) need to be avoided at all costs. Some companies generally disallow the use of chat services on their shared servers for these reasons. Switching to a dedicated webserver will be a clean and easy solution when reaching shared hosting limitations.