On 2016-09-19 13:34, Sergi Almacellas Abellana wrote:
> El 19/09/16 a les 10:26, Ali Kefia ha escrit:
> > We faced this problem last year and worked on scaling trytond this way
> > 
> >   * Shared Cache on Redis
> >   * Load balance with Nginx
> >   * Sync mechanism via redis PUB/SUB to reload Pool
> > 
> > Description of Coog (trytond spécialized ERP)
> > here: http://coopengo.com/coog-v1-6-nouvelle-architecture/
> > Implementation on a trytond fork: https://github.com/coopengo/trytond
> > For more details or help using it, send me an email
> AFAIU you need the redis chache and the sync mechaninsm because you have the
> wsgi servers running in different machines. Am I right?

You do not need anything for the cache even if it runs on different
machine. But memory for cache will be used per process.

The pool invalidation is not supported but as the module management is
slowly moved to trytond-admin. I think there are no needs to implement

Cédric Krier - B2CK SPRL
Email/Jabber: cedric.kr...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

You received this message because you are subscribed to the Google Groups 
"tryton-dev" group.
To view this discussion on the web visit 

Reply via email to