Hi
On Tuesday, September 20, 2016 at 2:19:12 AM UTC-5, Sergi Almacellas
Abellana wrote:
>
> El 19/09/16 a les 18:07, Ali Kefia ha escrit:
> > => We will give werkzeug a try (if you have a document that helps on
> > configuration, please share)
> Using uwsgi you can run trytond with the
El 20/09/16 a les 12:02, 'Korbinian Preisler' via tryton-dev ha escrit:
I had the problem that my config files had a custom location. So i had
to create this wsgi.py:
https://gist.github.com/timitos/f74e5c6b5c75064f9c9d2417f23e6cad
For me this can be improved by allowing setting the trytond
Le mardi 20 septembre 2016 11:16:39 UTC+2, Sergi Almacellas Abellana a
écrit :
>
> El 20/09/16 a les 10:58, Ali Kefia ha escrit:
> >
> >
> > Le mardi 20 septembre 2016 09:19:12 UTC+2, Sergi Almacellas Abellana a
> > écrit :
> >
> > El 19/09/16 a les 18:07, Ali Kefia ha escrit:
> >
Le mardi 20 septembre 2016 09:19:12 UTC+2, Sergi Almacellas Abellana a
écrit :
>
> El 19/09/16 a les 18:07, Ali Kefia ha escrit:
> > => We will give werkzeug a try (if you have a document that helps on
> > configuration, please share)
> Using uwsgi you can run trytond with the following
El 20/09/16 a les 09:48, 'Korbinian Preisler' via tryton-dev ha escrit:
Hi Ali,
On 20.09.2016 09:32, Ali Kefia wrote:
Le mardi 20 septembre 2016 09:19:12 UTC+2, Sergi Almacellas Abellana a
écrit :
El 19/09/16 a les 18:07, Ali Kefia ha escrit:
> => We will give werkzeug a try (if you
Le mardi 20 septembre 2016 09:49:22 UTC+2, Timitos a écrit :
>
> Hi Ali,
>
> On 20.09.2016 09:32, Ali Kefia wrote:
>
>
>
> Le mardi 20 septembre 2016 09:19:12 UTC+2, Sergi Almacellas Abellana a
> écrit :
>>
>> El 19/09/16 a les 18:07, Ali Kefia ha escrit:
>> > => We will give werkzeug a try
Hi Ali,
On 20.09.2016 09:32, Ali Kefia wrote:
>
>
> Le mardi 20 septembre 2016 09:19:12 UTC+2, Sergi Almacellas Abellana a
> écrit :
>
> El 19/09/16 a les 18:07, Ali Kefia ha escrit:
> > => We will give werkzeug a try (if you have a document that
> helps on
> > configuration,
Le mardi 20 septembre 2016 09:19:12 UTC+2, Sergi Almacellas Abellana a
écrit :
>
> El 19/09/16 a les 18:07, Ali Kefia ha escrit:
> > => We will give werkzeug a try (if you have a document that helps on
> > configuration, please share)
> Using uwsgi you can run trytond with the following
Le lundi 19 septembre 2016 18:40:03 UTC+2, Cédric Krier a écrit :
>
> 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
El 19/09/16 a les 18:07, Ali Kefia ha escrit:
=> We will give werkzeug a try (if you have a document that helps on
configuration, please share)
Using uwsgi you can run trytond with the following command:
uwsgi --http :9090 --module trytond.application:app --processes 4
It's a start, for full
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?
> >
>
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
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:
>
>-
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
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
>
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
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
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
On 2016-09-14 07:28, Sergio Morillo wrote:
> El martes, 13 de septiembre de 2016, 10:54:51 (UTC+2), Sergi Almacellas
> Abellana escribió:
> 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)?
> >
>
El 07/09/16 a les 19:39, Sergio Morillo ha escrit:
Finally I used uWSGI following the example of previous wsgi tryton patch
[1] but using new trytond.application.app [2].
Are you using multiple workers?
I'm a little bit curious about how you manage the tryton cache. Are you
using the standard
Finally I used uWSGI following the example of previous wsgi tryton patch
[1] but using new trytond.application.app [2].
[1] http://downloads.tryton.org/TUL2014/WSGI_Deployment.pdf
[2] http://doc.tryton.org/4.0/trytond/doc/topics/start_server.html
El viernes, 26 de agosto de 2016, 18:07:17
21 matches
Mail list logo
