Support varnish cache.
Would you mind to try Nginx caching in Plesk Onyx 17.8 Preview?
This would be very helpful to get your experienced feedback here http://www.surveygizmo.com/s3/4165754/Plesk-17-8-Preview
"Edge sides include ESI can be achieved via Varnish cache sitting between nginx and apache." - YES -pls!
IT WOULD BE GOOD TO HAVE VARNISH CACHE AND / OR MAMECACHED DIRECTLY IN THE APPLICATIONS, WITHOUT PASSING FROM THE DOKER .. IT WOULD BE FANTASTIC ALL THIS. SEMPLIFE VERY WORK
This guide is for the older version of Magento platform. We recommend you to use the latest version of Magento. https://www.cloudways.com/blog/how-to-configure-varnish-cache-magento/
Warren Camilleri commented
i for one am new to plesk and docker, i would be lost on how to test it up, but to have the option to run it like i can ran nginix within the webspace or like redis from php settings would be great.
Also note Having Varnish hits, it doesn't hit your app at all. Something like redis etc is still slow.
Still having both Varnish, redis can be optional.
Edge sides include ESI can be achieved via Varnish cache sitting between nginx and apache.
Thus nginx will terminate ssl, full cached page if found on Varnish will be served directly. Cache miss will be serviced by apache.
This cannot be achieved via nginx + apache.
This test case is important for many business cases like magento, high traffic full page cached sites etc. Currently only Centos webpanel supports it and cpanel has a third party addon.
Also Varnish has VMODS and some are pretty essential like say, Geoip module.
Plesk dev can test Varnish , and can think to provide is as optional. Varnish is not everyone's cup of tea, still It does have strong business case like magento. It's essential for many clients now, thus having it optional does seems very useful. As for support part, plesk should focus on just the installation and ease to use it and basic funtion. Configuration support is out of scope and community or Internet can provide help.
Marco Marsala commented
Varnish cache is a full page cache. Nginx in Plesk is not configured to use caching. Implement Varnish or enable cache in Nginx.
Matt Bodell commented
Moving from cPanel to Plesk would be essential if you supported varnish!! :D
We love 12.5 but are replacing with cPanel solely because of not having Varnish.
And those who claim you don't need it etc - what do you know what I need? If I want it, if I think it helps my site, that is my prerogative and my business. There are arguments for both sides, there are believers on one, believers on the other. But there is no denying that many want it and are trying to hack-install it on Plesk 12. A quick google will tell you so. The people HAVE spoken - it IS needed.
I see plesk 12.5 has many options for nginx and php-fpm now in relation to php version.
I would still keep my vote on varnish as i think it would be good for people with really badly configured servers to get better performance easily. ;)
Ps this would be good for me instance. Nginx PHP needs php 5.3. Getting seriously old. Will be updating to newest magento that needs 5.4 Min. I would have the option of placing Varnish infront of apache and using any php verison i needed. Same for many other apps.
As magento 2.0 will feature varnish 4 compatibility, this could be a good option, to run varnish in front of nginx or apache. Or both would be good options.
Benchmarks i have seen have not shown varnish to be that much faster than nginx for magento, but im pretty sure this is a feature many people want and it maybe better in other bench marks.
Myself i would maybe not use varnish, as my servers runs amazingly with nginx. But it would be a great tool to run infront of apache giving access to more php versions for customers that need it etc and giving them a powerful caching front end, giving plesk more versatility and appealing to more customers.
The extension of plesk, must be able the customer to enable/disable the varnish cache for domain, so, if for magento is a nightmare, simply disable it from control panel and will works fine! :)
Varnish is a nightmare especially for carts like Magento, there are already magento extension that do the same thing as varnish without all the hassle for really low prices. This is just a total waste of time.
Can be better if you add also an option for enalbe/disable varnish cache for each domain/subdomain, varnish is an very good cache for website for example wordpress, joomla, drupal many provider offer this type of cache.
Many provider offer cache with varnish but with cpanel, so I think that is better to add also this possibility directly from plesk.
Andy Bird commented
Varnish is a caching proxy that simply serves 'pre-compiled' pages directly from RAM without having to be generated through nginx/apache/php leading to a massive reduction in page load times on the second and subsequent visits.
While integrating it into a control panel will be tricky it should be possible and would be a powerful addition to plesk.
Any news about performance improvements with varnish, redis or CDN administration? Whats the way plesk will go?
Varnish is actually very popular among high-traffic websites:
"Varnish is used by a great number of high-profile, high-traffic websites including online newspaper sites such as The New York Times, BBC, The Guardian, The Hindu, social media and content sites such as Facebook, Twitter, Vimeo, Tumblr and many more. Of the Top 10K sites in the web, around a tenth use the software." Source: https://en.wikipedia.org/wiki/Varnish_(software)
This thread also lacks an simple explanation why Varnish would be useful (or I read past it, in that case, sorry).
In stead of running PHP code every time a page loads, Varnish lets Apache run the PHP code once en stores the website Apache produced in memory. The next time this saved page is shown, without the need of running PHP code. This way a server could serve a lot more pageviews per second.
Webshops and such are tricky, but it's very possible to get those to run without problems with Varnish.
@Ben: You dont seem to know what you are talking about. Varnish is something totally different than Spdy. Varnish is a caching reverse proxy server, Spdy is an alternative/addition to the HTTP protocol which makes for slightly faster webpages due to compression and optimalisations.
As I've written in this thread before, Varnish is _not_ a drop-in addition to Apache. Varnish needs to be configured to work properly with various CMS and shop software like Magento. Thus, the only way to achieve supporting Varnish is if Plesk is aware of the software running on a users website. This is way beyond the scope of Plesk.
I very much doubt that 'all major' sites use Varnish. I believe the use of Varnish is actually in decline and other solutions such as Redis object caching is now the more obvious choice. Redis is just an example, there are lots of other data stores that can be used to achieve better performance.