Varnish cache
Varnish is currently on the roadmap for the Byte non-Magento platform. For Magento, it is not planned yet. For context, read https://www.jeroenvermeulen.eu/en/blog/varnish-versus-hhvm/ about the advantages of HHVM above Varnish.
AdminHypernode Dev Team
(Developer, Hypernode BV)
shared this idea
We now support Varnish on Go Big Hypernodes. http://support.hypernode.com/changelog/release-1767-varnish/
-
Hey Luk,
Where did you hear that rumour ;)
Varnish is currently not very near on the Roadmap. It has been discussed though, but because Varnish needs _loads_ of free memory to cache stuff, this is not very suitable on Hypernodes.
Also, in my experience, Lesti FPC on disk is almost as fast and much more user-friendly.
-
Luk van den Borne
commented
I've heard rumours that Varnish is on the roadmap. While this is great, I do hope Byte ensures there is an appropriate amount of room for VCL customisation. With only a central, unmodifiable VCL, the usefulness of Varnish will be greatly inhibited.
Or at least have a very flexible VCL that allows all Varnish operations to be called dynamically via for example additional X-Varnish headers with regex support.
-
Jeroen Boersma
commented
I have a configuration available where Nginx still exists listens on port 80, so multidomain and ssl can be configured in Nginx, and Varnish can be configured for specific domains.
Offcoarse it means that Nginx also has to listen on another port for the traffic which can't be handeled by Varnish.
I know it looks a bit overkill, but some things are easier to handle from Nginx.