Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
litespeed_wiki:php:improve-performance [2017/12/21 19:51] Jackson Zhang |
litespeed_wiki:php:improve-performance [2019/04/04 13:46] Jackson Zhang |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| * Upgrading to a higher CPU LiteSpeed license should provide more processing power. | * Upgrading to a higher CPU LiteSpeed license should provide more processing power. | ||
| - | * If the server has enough free memory, put PHP sessions and opcode cache disk storage under /dev/shm. If server I/O wait is high, enable AIO logging. | + | * If the server has enough free memory, put PHP sessions and opcode cache disk storage under /dev/shm. |
| + | * If server I/O wait is high, enable AIO logging. | ||
| + | * Does the domain hit CloudLinux LVE IO Limit? Use ''lvetop'' to verify if IO is reaching the defined maximum (xMB/s). | ||
| * Have you enabled the timezonedb module for your PHP? We do see poorer performance when people move to a cloud server with shared storage, the I/O latency could cause trouble. Without PHP timezonedb module with built-in DB, it may not have a huge impact on a server with the local disk but it will be very costly for a cloud server with shared storage since PHP will scan hundreds of directories. | * Have you enabled the timezonedb module for your PHP? We do see poorer performance when people move to a cloud server with shared storage, the I/O latency could cause trouble. Without PHP timezonedb module with built-in DB, it may not have a huge impact on a server with the local disk but it will be very costly for a cloud server with shared storage since PHP will scan hundreds of directories. | ||
| * Check your "top" output to determine which processes are using too much CPU/memory. Buggy PHP code could be causing these performance issues. | * Check your "top" output to determine which processes are using too much CPU/memory. Buggy PHP code could be causing these performance issues. | ||