Re: [tryton-dev] Re: WSGI application server for Tryton

2016-09-19 Thread Cédric Krier
On 2016-09-19 09:07, Ali Kefia wrote: > > > Le lundi 19 septembre 2016 17:40:03 UTC+2, Cédric Krier a écrit : > > > > On 2016-09-19 08:19, Ali Kefia wrote: > > > the issue with cache on multi workers is that invalidation does not > > > propagate. > > > > Could you proof your statement? > > >

Re: [tryton-dev] Re: WSGI application server for Tryton

2016-09-19 Thread Ali Kefia
Le lundi 19 septembre 2016 17:40:03 UTC+2, Cédric Krier a écrit : > > On 2016-09-19 08:19, Ali Kefia wrote: > > the issue with cache on multi workers is that invalidation does not > > propagate. > > Could you proof your statement? > Context: multi-process. I could miss something (that is

Re: [tryton-dev] Re: WSGI application server for Tryton

2016-09-19 Thread Cédric Krier
On 2016-09-19 08:19, Ali Kefia wrote: > the issue with cache on multi workers is that invalidation does not > propagate. Could you proof your statement? > And since using db is counter cache principle, we took Redis. I do not understand the reasoning. > side effect advantages were: > >-

Re: [tryton-dev] Re: WSGI application server for Tryton

2016-09-19 Thread Cédric Krier
On 2016-09-19 05:32, Ali Kefia wrote: > May be I missed something but it is worth asking a question: > When we have 2 workers, W1 and W2, working on an instance (call it a > product), how to manage this situation: > >- W1 added product to cache (from database) >- W2 modified product and

Re: [tryton-dev] Re: WSGI application server for Tryton

2016-09-19 Thread Ali Kefia
Le lundi 19 septembre 2016 14:05:02 UTC+2, Cédric Krier a écrit : > > 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 >

Re: [tryton-dev] Re: WSGI application server for Tryton

2016-09-19 Thread Cédric Krier
On 2016-09-19 04:52, Ali Kefia wrote: > We tried to investigate ir.cache and did not succeed to ensure propagating > invalidation What did you miss? -- 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

Re: [tryton-dev] Re: WSGI application server for Tryton

2016-09-19 Thread Cédric Krier
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

Re: [tryton-dev] Re: WSGI application server for Tryton

2016-09-19 Thread Ali Kefia
Le lundi 19 septembre 2016 13:34:06 UTC+2, Sergi Almacellas Abellana a écrit : > > 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

Re: [tryton] Tryton client hung up when trying to send PDF to email and open automatically the same report

2016-09-19 Thread Jean Cavallo
2016-09-19 10:18 GMT+02:00 Cédric Krier : > > 2016-08-04 17:27 GMT+02:00 Fabián : > > - Patch trytond to connect to this running instance using pipe > > The patch to replace wait by communicate is interesting as there is a > warning in the doc: >

Re: [tryton] Tryton client hung up when trying to send PDF to email and open automatically the same report

2016-09-19 Thread Cédric Krier
On 2016-09-19 09:54, Jean Cavallo wrote: > 2016-08-04 17:27 GMT+02:00 Fabián : > - Patch trytond to connect to this running instance using pipe The patch to replace wait by communicate is interesting as there is a warning in the doc:

Re: [tryton] Tryton client hung up when trying to send PDF to email and open automatically the same report

2016-09-19 Thread Jean Cavallo
2016-08-04 17:27 GMT+02:00 Fabián : > - Many times Tryton hang up. Seems as it happens in the process when > convert ODT to PDF. In server I see there a lot of processes in background. > I put a few of them [2]. When processes are hang up, it is no possible to > pay any