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)
Implementation on a trytond fork: https://github.com/coopengo/trytond
For more details or help using it, send me an email
Sorry if it is still a custom code, we plan to discuss all this stuff in
TUB 2016 and hopefully get part of them in tryton out of the box.
Le mercredi 14 septembre 2016 16:28:35 UTC+2, Sergio Morillo a écrit :
> El martes, 13 de septiembre de 2016, 10:54:51 (UTC+2), Sergi Almacellas
> Abellana escribió:
>> El 07/09/16 a les 19:39, Sergio Morillo ha escrit:
>> > Finally I used uWSGI following the example of previous wsgi tryton
>> >  but using new trytond.application.app .
>> Are you using multiple workers?
> Four workers like example does.
> I'm a little bit curious about how you manage the tryton cache. Are you
>> using the standard implementation or using another backend (i.e: Redis)?
> Standard implementation. I'm still newbie in tryton and unfamiliar with
> tryton cache management problems (if exist). So I would appreciate your
> comments about it.
>> Also: how you manage to reload the workers when a new module is
>> updated/installed. Do you reload the services manually?
> Manually with supervisord.
>> Sergi Almacellas Abellana
>> Twitter: @pokoli_srk
You received this message because you are subscribed to the Google Groups
To view this discussion on the web visit