[ixpmanager] some questions re: IXP 5

Athanasios Douitsis aduitsis at noc.ntua.gr
Thu Oct 31 14:28:56 GMT 2019


On Thu, Oct 31, 2019 at 02:19:24PM +0000, Barry O'Donovan wrote:

> 
> 
> Athanasios Douitsis wrote on 31/10/2019 10:57:> Wait, in config/cache.php
> there are 7 possible CACHE_DRIVER values. Are
> > you saying that only 'memcached' is valid?
> 
> What I'm saying is:
> 
> > It may well work for some parts of it but there's actually two caching
> > mechanisms in the backend of IXP Manager: Laravel and Doctrine ORM. The
> > recommended and supported caching mechanism is memcahced which 'just works'
> > for both.
> 
> The sample .env.example file has the two elements set by default as:
> 
> CACHE_DRIVER=array
> DOCTRINE_CACHE=array
> 
> I.e. no cache so it will work out of the box. This is perfectly fine by the
> way - modern servers will serve IXP Manager pages in their sleep without
> caching. In our installation instructions we say that Memcached is optional
> but recommended.
> 
> The automated installation script installs and activates Memcached.
> 
> 
> Again, the Laravel and Doctrine caching mechanisms are different and not
> shared. What backends and how Laravel supports them is different to
> Doctrine.
> 
> You can play around with other ones no problem but our position is that
> array and memcached are the supported and tested caches and we have neither
> used nor recommend any others for the IXP Manager project.
> 
> 
> We try to reduce complexity in IXP Manager in so far as possible and so I
> don't see array or memcached as being the two options changing to be honest.
> 
>  - Barry

Hello Barry,

That's a perfectly good answer :-), we've had array with our production
4.8, we'll just keep using array with 5.2. I erroneously had the
impression that there might be some spectacular benefit from switching
to another driver.

Thank you very much for the clarification!,
Athanasios


More information about the ixpmanager mailing list