|PHP version||-||7.0.x||PHP 7.0.x, depending on the circumstances, this version offers a possible performance increase of up to 25-30% (PHP stack).|
|Bytecode cache||APC||ZendOpcache + APCu||Installing and configuring a Bytecode cache is more than recommended - it will likely increase PHP stack execution by an additional up to 25%.|
|MySQL||MySQL 5.5.x||MySQL 5.6.x or MariaDB derivate||If possible you should make use of the latest major productive MySQL version available. This will positively affect the execution of joins and subselects and read accesses MySQL sollte in der aktuellen für Produktivzwecke freigegebenen Major-Version eingesetzt werden, da es hier deutliche Verbesserungen bei der Ausführung von Joins, SubSelects und Lese-Zugriffen auf die Datenbank gegeben hat.|
|webserver||Apache 2||Nginx||If your shop generates particular large amounts of traffic, you might consider an alternate webserver such as e.g. Nginx.|
|Debugging / profiling||-||-||Make sure there are no profiling tools like xDebug or XhProf active and running on your server. Those will negatively affect PHP execution. The same is true for any Shopware debugging & benchmark plugin. So you should never use them in a productive environment.|
With every new iteration of Shopware there are performance improvements to be expected. Always keeping your software up-to-date should be your admin's first priority.
A hoster should resemble the aspired range of expertise in its offer. There should be an equally fitting upgrade path available, so that hosters can alter their offers according to the development and growth of your shop. You should consider the following topics:
Generally we recommend accepting services from one of our certified web hosters. A current list of hosters can be found following this link: Shopware hosting partner.
When measuring a shop's performance, loading times can only be an indicator for an expected level of performance. Characteristics present in your shop, ranging from item count to internal structure or momentary capacity utilisation will always have a significant influence on palpable loading times.
To generate comparable measurements, we recommend to install the Shopware demo data plugin before running tests in your shop. Firebug is a browser extension which can be installed directly via your browser. If installed it will display load times for every page component in your browser's networking tab.
Particularly relevant are the entire webpage's load times - most likely the first entry of the list. To gather relevant measurements you should load the landing page, listing pages and details pages several times and note all loading times. By calculating the means you will receive meaningful statistics on your shop's performance.
Call the benchmark using a linux shell:
ab -n 10 -c 1 http://HOMEGPAGE_URL / CATEGORY / DETAILPAGE
Here you should go for the median of all connection times (= total time).
|Identify problematic component||customer / hoster||Try and localize the source of the performance drops. Possibly this could be your webserver, the database server, your PHP stack and so on.|
|Analysing slow SQL queries||hoster||What database queries affect the overall performance of your shop?|
|Analysing the hosting platform||hoster / customer|
Do you have a hosting environment suitable for the size and the aggregated traffic of your particular shop? Do you use current and recommended server components? Do you employ dedicated servers instead of vhostings or webspace packages? Do you run any other applications apart from Shopware on your server?
|Accessibility||customer||Is there an ERP system cloggin up the connection with large amounts of data? Are there regular tasks running on your shop server, potentially lowering the performance.|
The standard configuration of many distributions is not ideally suited for productive environments. But don't worry, there is a script for that! "Mysqltuner" provides hints towards suboptimal configuration and parameter settings.
wget http://mysqltuner.com/mysqltuner.pl chmod +x mysqltuner.pl ./mysqltuner.pl
Set the attribute optimizer_search_depth = 0 in your MySQL configuration. Read more.
In case you have defined your own sorting criteria here, you should make sure there is an index in your database for each of the table's columns.
There are several different processes active when one of your shop's pages is accessed. For example SEO links are generated, the search engine's cache is generated as well as the necessary data for displaying top selling items or other items of interest based on similar customer behaviour. Thoroughly check if and how using this function may benefit your enterprise and consider switching the update strategy from "live" (per page request) to "cronjob" (cumulative, time-controlled). To do so navigate to Configuration > Cache/performance > Cache/performance > Settings (tab).
Look for the entries SEO (1), Search (2), Top seller (3) and Referral Marketing (4) to make your changes there. To make use of cronjob functionalities, you first will have to install two custom plugins, "Cron" and "CronRefresh". With these plugins you can time control server requests and should schedule them, most likely towards night time. If you are not sure how that works, kindly refer to this wiki article: Cronjobs.
With Shopware you can make use of caching instead of live fetching all the data for each user from the database. As each database access uses up scarce web ressources, consider activating http- caches. This will create a cache file, that incorporates the most important information from the article's listing and its details page, therefore preventing unnecessary database queries. This will also make browsing your shop a bliss as it will improve the performance greatly. For keeping prices up-to-date, this cache is invalidated when prices change!
With the cronjob we created above, we made sure the cache file doesn't grow too big, as it is deleted regularly (standard value: every 24h). This has proven to be quite practical as the http-cache might grow by 1-2GB each day if frequently used. Activate the http cache via Configuration > Cache/performance > Cache/performance > Settings (tab) > Http cache and check the plugin and all changes made for compatibility with your shop. It may be wise to make a test run before going live with the changes you made.
There are not only a few cases in which the use of plugins severely impacted a shop's performance. To see if that might be the case in your shop, too, it might be wise to deactivate all third-party plugins and compare the frontend performances with and without activated plugins.
An easy way of doing this is to conduct an SQL query in a test environment. Both queries shown hereunder can be run in phpMyAdmin and will deactivate a plugins that are not part of the default Shopware configuration.
UPDATE `s_core_plugins` SET `active`= 0 WHERE `source` = 'Community' UPDATE `s_core_plugins` SET `active`= 0 WHERE `source` = 'Local'
Step-by-step instructions are to be found in the following wiki article: Shopware SQL.
Alternatively you may want to use the Plugin safe mode provided via the Plugin manager from Shopware 5.3 onwards.
Once the shop runs smoothly again, you can try and make out the plugin impacting your shop's performance by reactivating the third party plugins step-by-step. You can also re-evaluate the need for each individual plugin and tidy up your shops backend a little.
Shopware out-of-the-box comes with a "Debug" plugin, that is able to monitor and benchmark individual processes on a server. It will provide you with sufficient information on e.g. the duration of page requests and it will hint at processes e.g. database queries, controller etc. that might slow down individual requests.
Have you ever heard about extended caching, namely ZendOP and APCu? Either way, you should consider installing and activating both in your shop to boost performance even more. To evaluate the current performance levels of a shop, use the tools found in Configuration > Caches/performance > Caches/performance > Settings > Performance checks
Shopware gathers information on your system configuration and lists them in Configuration > System info.
Here you find entries like "memory_limit" (1). Exceeding the memory limit e.g. will negatively impact performance. Be aware that memory limits can be tweaked and e.g. virtually enlarged, making a thorough examination of your system worthwhile.
Visiting Configuration > Theme manager > Settings you have the opportunity to deactivate compiler caching. This is generally advised during the normal productive shop cycle. Because compiler caching greatly slows down a shop, it should only be used when you are developing and tweaking on the infrastructure anyway.