Our Magento partner SupportDesk has produced the seventh version of the Optimised Magento Image. The speed of this recordbreaking Magento solution has been further improved and a lot of optimalisation tools have been added.
A new version of our Optimised Magento Image is available. The optimalisation of this image is done by our Magento partner SupportDesk. This party used to be known as Jira ICT and is the number one Magento consultant in the Netherlands.
The most important change is using PHP 5.4, this upgrade yields an extra 25% extra speed. With the use of PHP 5.4 caching methods, like Memcache and APC, that were available in Magento Image V5, are now unavailable or outdated. In the place of these caching methods we are now using the more efficient Redis.
Online sales figures are incredibly sensitive to a site's loading speed. This is why we have an optimised CloudVPS Image for Magento available. With the help of this product we currently host a large number of quick web shops in our cloud.
For Magento and Joomla optimalisation we have partnered with Jira ICT, the number one Magento trainer and consultant in the Netherlands. After your shop is placed on the virtual server Jira will perform a free, one hour, optimalisation.
Because commercial sites need to be increasingly fast we released a CloudVPS Image that was completely optimised for Magento & Joomla in February of last year. We developed this image together with our partner Jira ICT , the top Magento & Joomla trainer and consultant in the Netherlands. This image is now one of our most popular configurations. Over the last year a lot of developments have occurred and that is why we are now releasing a completely new version of this optimised CloudVPS Image.
The most important change was that we moved from suphp to mod_ruid2. We incorporated suphp in the original image because it helps to manage filesystem rights by assigning a unique process to every user that has a request. This can lead to a drop in performance however as a lot of new processes have to be spawned during busy times. mod_ruid2 still assigns a process to a single user but allows for processes to change user so they dont have to be created (forked) exactly when the server is experiencing high load.