Include memcache and settings for ram etc as standard.
Since Plesk Onyx you will be able to install memcache as a Docker container and configure http(s) proxy rule for it to map to your web app.
Docker and proxy rules are available in Plesk Onyx Preview already, you can try it here https://talk.plesk.com/threads/plesk-onyx-preview-and-feedback.337172/
Michael Lohr (michidk) commented
How do I use mecached with Plesk? Where to define the proxy rules?
Please, do not tell us to use Varnish or NGinx...
Please just provide memcached as a php settting for 7.0, 7.2 and 7.2, this is all we need !
No, not something like docker...
That's the worst implementation.
Jan Löffler commented
sure Jan, with pleasure! We launched Plesk Onyx 17.8 last month which comes with free NGINX caching. You can control all cache settings easily by domain from the Plesk UI. Based on our intensive benchmarks with Varnish, NGINX, Memcached, Redis, WordPress Caching plugins (e.g. WP Super Cache, WP Rocket, W3 Total Cache) NGINX had the best out-of-the-box results. This is why we integrated it. With Varnish we achieved the very best results, but it requires a lot of experience in tuning. To simplify the very best caching, we just launched "Speed Kit" today which is Varnish and CDN based with an additional super efficient In-Browser Caching. This Pro Extension for Plesk was build with a Partner of Plesk that have put 30 man years in caching experience into the product. The result ist amazing. I would be very interested in your feedback!
Hi Jan L, you mentioned to "expect a new experience around caching in March 2018". This is now one month ago, can you elaborate a bit more if we can still expect this and how this experience should look like?
Docker also doesn't work with CloudLinux. The Docker solution is nowhere good enough!
Jan L commented
@Armin: We'll deliver something that suits your needs. Expect a new experience around caching in March 2018.
Armin Kirchhoff commented
i have a similar setup, i am not allowed to run a extra vm inside my vm.
thereforce i please you to also add a other option to run this without the overhead of a extra vm(docker) only to run ONE similar service more on a server, which usally runs on a debian/ubuntu based system which leads only to add one more service physically
You could also install it on an different machine!
GO FOR BARE METAL PHP70, 71, 72 !!
@Wack Docker is supported in Virtuozzo 7. If you can convince your provider to upgrade Virtuozzo you can also use Docker with Plesk.
Docker container are not working in some virtual environments. Our Provider uses Parallels Virtuozzo and it is not allowed to use Docker because of trouble with Virtuozzo . So Docker doesn´t help us.
BARE METAL! - do it and do it php7 ;-)
otherwise we could start an VM inside the VM with a Docker inside handling memcached :-D
With so many websites now being powered by web applications like WordPress, it just seems like Memcached should already be a extension option in the Plesk Php extensions. I really hope this gets treated more seriously and added as soon as possible.
I can´t use memcache as a Docker container, because Docker is not working on the VM
Need memcached in php7-fpm support in plesk.
Benjamin Hodgetts commented
That's not really the same thing and, for customers that aren't as savvy, isn't really suitable. Having memcache as a PHP module should be simple and there's nothing (technically) stopping it being added to existing Plesk 12 setups.
dont forget to vote for this one
Benjamin Hodgetts commented
Unless Couchbase is a "drop-in" replacement for PHPs Memcache(d) modules then that wouldn't be viable at all.
Our customers need PHP's Memcache module specifically, not something entirely different because the software they want to use (e.g. off-the-shelf CMS systems or plugins for those CMS) need it or offer additional functionality when PHP's Memcache implementation is available.
Jay Owen commented
i would suggest to use couchbase to supply memcached services. it would be easier to integrate and is protocol compatible with memcached.
It would also allow the plesk node to participate in a couchbase cluster (possibly using other plesk nodes as members)- meaning a plesk node can reboot and the cache would not need to be re-saturated.
if you have many sites that rely on caching on a single node, this is helpful, as cachestorms from a reboot could cripple a dense plesk node.