-
Odoo for NGO's
Michael Karrer
-
Have you got a great idea for a presentation?
Odoo Community Association (OCA)
-
Job and Service Management for Install and Construction
Wolfgang HallDone
-
Testing best practices, tips and tricks
Simone OrsiDone
-
EDI made simple
Simone OrsiDone
-
Odoo BDD? What's that?
Pierre VerkestDone
-
Vault: Managing passwords in Odoo
Frederik Kramer and Florian KantelbergDone
-
Complex Calculations on Odoo using Google sheets
Ossi MäntylahtiDone
-
Working offline without leaving Odoo
Pedro M. BaezaDone
-
Odoo User Access through Role Policy: a Game Changer
Els Van Vossel, Richard Varghese and Luc De MeyerDone
Lead developer at Sunflower IT, an Odoo integrator in the Netherlands.
Sometimes we are confronted with bad performance in Odoo and not sure where to look in the code. Older versions or custom code can cause database locking conflicts and memory issues. Profilers such as py-spy can be useful, but have to be fired at the exact right moment and at the right worker to give useful information.
We developed a set of non-intrusive scripts that can be applied on production servers and monitor for locks and high memory usage, then profile the situation. These scripts can be used to quickly point to the offending code, even when just stepping into a new project and dealing with a very large codebases that you are unfamiliar with.
