Odoo Experience 2019
-
Unleash the Power of GraphQL with Odoo
Stéphane BidoulDone
-
The Odoo Javascript Framework
Gery Debongnie, Lead Developer - OdooDone
-
CSR: an Emerging Innovation Paradigm
Bastien Van WylickDone
-
How to Handle a Performance Issue?
Nicolas Seinlet, Developer - OdooDone
-
Load Testing: How to Stress Your Odoo with Locust
Michael Vannerom, Developer - OdooDone
-
Gaining and Maintaining the Trust of Your Customers: an Inside Job
Julie SafferyDone
-
How to Deal with Custom Code for an Upgrade
Patricia Daloze, Developer - OdooDone
-
GDPR 1 Year Later
Olivier Dony, Platform & Security - OdooDone
-
StorySelling - Telling Stories that Improve Your Bottom Line
David NelsonDone
-
Odoo: Boosting Business in a Multichannel Approach
Christophe GeoffroyDone
Odoo developer from TinyERP 4.2 CTO of Vauxoo Gold Partner
Running profiling from live production without reboot service for any version of Odoo.
There are a lot of performance issues related to the environment. If you start checking what is wrong using a test environment, you can not reproduce it even if you are using the exact environment. Using tools where you can check a performance issue from a live production is a great way to check it. It is important to avoid rebooting the Odoo service since it is used live.
Other kinds of tools require a reboot, and they work using just one worker like cProfiling, line-profiler, where a change in the code to enable is required and a monkey patch to Odoo is needed to make it compatible.
You will learn how to enable profiling for more than one worker. The tools used are: pyflame, postgres log and pgbadger All can be started without modifying code, so without rebooting Odoo service.