Community mailing list archives
Re: Odoo Performance and concurrency locksby
Akretion, Raphael Valyi
this is an old topic and as there will be the opportunity to make important changes in the new release I'll suggest again to study something: if I'm not wrong, in the Tryton fork they created a "readonly cursor", that is any request hitting the server for read, fields_view_get or other strictly read only requests will borrow a special cursor to the pool that that is readonly, so I guess this will overall be more efficient than the serialized transactions we use systematically in Odoo. Any idea?
On Mon, Sep 14, 2015 at 2:09 PM, Nhomar Hernández <email@example.com> wrote:
2015-09-14 10:52 GMT-05:00 Olivier Dony <firstname.lastname@example.org>:2b. As of PG 9.3, you should not see TransactionRollbackErrors caused by logins unless your transactions are actively updating user records themselves. This should not happen much with the standard Odoo distribution.IMHO, it is happening to me in several environments variations, if you ar open to fix this i can prepare for you a set of use cases.But yes with Psql > 9.3 it is not happening as frequent as others but it happends at the end,I think my frien we should look deeper on the algorithms to fix it in some point.regards.