:<\/strong><\/p>\n\n\n\n\u2018image_resize_lib\u2019 => \u2018imagick\u2019,<\/pre>\n\n\n\nNote:<\/strong> If Imagick is not installed on the server, explicitly forcing its use may cause errors. You should implement a check to ensure the component is available before using it.<\/p>\n\n\n\nAlso note that if you have \u201cauto\u201d in your config.local.php file next to image_resize_lib, then once you have imagick installed, it will be used by default.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Enable APCu for cache and Redis for storing sessions<\/h3>\n\n\n\n We recommend using APCu<\/strong> for caching in CS-Cart and Redis<\/strong> for storing user sessions. This separation helps reduce the load on the database and file system, speeding up request handling and improving overall application responsiveness.<\/p>\n\n\n\nHowever, it’s important to consider that introducing additional services like Redis increases the complexity of your infrastructure. It adds another potential point of failure, which also needs to be monitored and managed \u2014 for example, using tools like systemd or supervisord to ensure availability and automatic restarts.<\/p>\n\n\n\n
Additionally, storing cache in APCu means it will be held in the memory of each PHP process. This can increase overall RAM usage and may affect performance on systems with limited resources. APCu also works only with mod_php or php-fpm, and is not suitable<\/strong> for multi-server configurations where shared cache is required.<\/p>\n\n\n\nBefore adopting this approach, ensure your infrastructure is prepared to handle these specifics and that all components can operate reliably.<\/p>\n\n\n\n
$config['cache_backend'] = 'apcu';<\/pre>\n\n\n\n$config['session_backend'] = 'redis';<\/pre>\n\n\n\nEnabling these settings in your configuration file requires APCu (PHP 7.0+)<\/strong> and Redis<\/strong> to be properly installed and configured on your server. Before editing the configuration, make sure both APCu and Redis are available. If you’re unsure or need assistance, consult your system administrator or hosting provider.<\/p>\n\n\n\n<\/p>\n\n\n\n
Use mysqldump for backup<\/h3>\n\n\n\n Mysqldump<\/strong> is a server-side utility available on most modern hosting environments, and it’s widely recommended by system administrators for creating database backups. For reliable backups, it’s best to use mysqldump.<\/p>\n\n\n\nIn CS-Cart, support for mysqldump is available, but disabled by default<\/strong>. This is because on some hosting platforms, mysqldump may be unavailable, unstable, or require elevated permissions. As a result, CS-Cart uses a built-in PHP-based backup method by default, which offers broader compatibility but may be less efficient for large databases.<\/p>\n\n\n\nTo enable mysqldump for backups, add the following parameter:<\/p>\n\n\n\n
$config['tweaks']['backup_db_mysqldump'] = true;<\/pre>\n\n\n\nto the $config[‘tweaks’] array in your config.local.php file.<\/p>\n\n\n\n
Once enabled, CS-Cart will use mysqldump to create database backups \u2014 a faster and more resource-efficient method, especially beneficial for large projects, as it reduces the load on PHP processes during the backup operation.<\/p>\n\n\n\n<\/p>\n\n\n\n
Implement a backend lock in the cache generation processes<\/h3>\n\n\n\n In recent versions of CS-Cart, a new feature has been introduced to prevent simultaneous cache generation by multiple users<\/strong>. This is especially useful under high load conditions \u2014 for example, after clearing the cache or on the first run after deployment.<\/p>\n\n\n\nTo enable this protection, add the following line to your config.local.php file:<\/p>\n\n\n\n
$config['lock_backend'] = 'database';<\/pre>\n\n\n\nWith this setting, CS-Cart will use the database<\/strong> to store lock information, preventing concurrent execution of resource-intensive operations.<\/p>\n\n\n\nRedis<\/strong> is also supported as a lock storage backend, which is recommended for high-load projects, especially in distributed environments. To enable Redis locking, use:<\/p>\n\n\n\n$config['lock_backend'] = 'redis';<\/pre>\n\n\n\nImportant:<\/strong> Make sure Redis is available and properly configured in your CS-Cart installation. Using Redis can improve performance and reduce database load when handling locks.<\/p>\n\n\n\nThis mechanism not only helps prevent <\/a>server overload during cache generation, but also ensures correct order processing<\/strong>. In recent CS-Cart versions, the locking system is also used when interacting with payment systems like Stripe<\/strong> and PayPal<\/strong>. Without active locking, order statuses may be updated incorrectly, potentially leading to inventory inconsistencies and other critical issues in business logic.<\/p>\n\n\n\n<\/p>\n\n\n\n
<\/span>How to find and fix problems with CS-Cart performance without programming skills<\/span><\/h2>\n\n\n\nEven without coding skills, you can identify and fix performance bottlenecks<\/strong> in your CS-Cart or CS-Cart Multi-Vendor store. Below are practical tips and metrics to help you perform basic diagnostics on your own.<\/p>\n\n\n\nUse the Built-In CS-Cart Debugger<\/strong><\/h3>\n\n\n\nCS-Cart includes a built-in debug mode<\/strong>, which can be activated by adding ?debug to the URL. Once enabled, a “bug” icon will appear in the top right corner. Clicking it will reveal detailed information:<\/p>\n\n\n\n\nSQL<\/strong> \u2014 number and execution time of database queries<\/li>\n\n\n\nBlocks<\/strong> \u2014 block loading speed and memory usage<\/li>\n\n\n\nPage generation time<\/strong> \u2014 total time to render the page<\/li>\n<\/ul>\n\n\n\n<\/span>Key Metrics to Monitor<\/span><\/h2>\n\n\n\nMetric<\/strong><\/th>Recommended Value<\/strong><\/th><\/tr><\/thead>Page generation time<\/strong><\/td>\u2264 1 sec \u2014 excellent performance Database query time<\/strong><\/td>\u2264 0.1 sec \u2014 good performance Number of blocks from cache<\/strong><\/td>\u2265 5 out of 20 \u2014 acceptable, but the more blocks served from cache, the better the performance<\/td><\/tr> Block render time<\/strong><\/td>\u2264 0.1 sec \u2014 fast0.<\/p>\n\n\n\n
Tip:<\/strong> Enable the debugger and click through pages \u2014 you’ll see which blocks or modules are slow and where the bottlenecks are.<\/p>\n\n\n\n<\/p>\n\n\n\n
![\"MySQLdump\"](\"https:\/\/i0.wp.com\/www.cs-cart.com\/blog\/wp-content\/uploads\/mysqldump.jpg?resize=800%2C216&ssl=1\")
<\/figure>\n\n\n\n