Re: [tryton-dev] Tryton Modules Registry

2016-11-15 Thread Nicolas Évrard
* Aleksandar Stefanov [2016-11-10 17:04 +0100]: Hello everyone, Hello Aleksandar, We work with Tryton and since we couldn't find anything like "Tryton Modules Registry" with a list of all modules ever developed by anyone, we created a small web app for our own use which we called so. It

Re: [tryton-dev] Stateless Trytond

2016-11-15 Thread Jean Cavallo
2016-11-15 16:02 GMT+01:00 Mikhail Savushkin : > As long as we're talking about millions of DBs, this straightforward > approach wont work. Maybe another approach could be to group the pools per module combinations ? i.e. the pool for DB1 which has the same installed modules

Re: [tryton-dev] Stateless Trytond

2016-11-15 Thread Cédric Krier
On 2016-11-15 07:02, Mikhail Savushkin wrote: > Metrics are: > > > """ > DBs in Pool RSS, kBytes Added to memory, kBytes > 0 65,020 - > 1 86,576 +21,500 > 2105,520 +19,000 > 3

Re: [tryton-dev] Stateless Trytond

2016-11-15 Thread Mikhail Savushkin
Metrics are: """ DBs in Pool RSS, kBytes Added to memory, kBytes 0 65,020 - 1 86,576 +21,500 2105,520 +19,000 3114,520 + 9,000 4123,708

Re: [tryton-dev] Stateless Trytond

2016-11-15 Thread Jean Cavallo
2016-11-15 13:19 GMT+01:00 Cédric Krier : > On 2016-11-15 03:14, Mikhail Savushkin wrote: > > Now we have another blocker on the road - the Pool building process is > too > > long to be fired on every request. And we cant afford collecting Pools > for > > all of the DBs in

Re: [tryton-dev] Stateless Trytond

2016-11-15 Thread Cédric Krier
On 2016-11-15 03:14, Mikhail Savushkin wrote: > Now we have another blocker on the road - the Pool building process is too > long to be fired on every request. And we cant afford collecting Pools for > all of the DBs in memory, since it will eat all the available memory pretty > quick. Do you

[tryton-dev] Stateless Trytond

2016-11-15 Thread Mikhail Savushkin
Hi there! I'm a developer from semilimes. We're trying to use Tryton as a cloud ERP. So, unchaining trytond from some particular DB on launch was our first problem, which was solved thanks to Cedric's advices during the TUB'16 (thank you a lot for that, greatly appreciated!!) Now we have