Profiling en Odoo modificando el odoo.conf
Un pequeño truco, que me esta ahorrando mucho tiempo, revisando el archivo de ejemplo de odoo.conf, me encontré con los distintos valores que puede tener cada entrada del archivo de configuración de Odoo. Es interesante las opciones del log_level
# log_level: | |
| # any value in the list below. Odoo changed the log_level meaning | |
| # here because these level values are mapped to a set of predefined | |
| # 'module:log_level' pairs. These pairs are listed next to the log-level. | |
| # You could get the same result by using the log_handler option | |
| # | |
| # | |
| # LOG LEVEL / log_handler: module:log_level | |
| # ---------------------------------------------------------------------------- | |
| # info / [':INFO'] | |
| # critical / ['openerp:CRITICAL', 'werkzeug:CRITICAL'] | |
| # error / ['openerp:ERROR', 'werkzeug:ERROR'] | |
| # warn / ['openerp:WARNING', 'werkzeug:WARNING'] | |
| # debug / ['openerp:DEBUG'] | |
| # debug_sql / ['openerp.sql_db:DEBUG'] | |
| # debug_rpc / ['openerp:DEBUG','openerp.http.rpc.request:DEBUG'] | |
| # debug_rpc_answer / ['openerp:DEBUG','openerp.http.rpc.request:DEBUG', | |
| # 'openerp.http.rpc.response:DEBUG'] |
Entonces, despues de modificar el archivo de configuración de Odoo volví a ejecutar la operación problemática. Y me encontré con la siguiente sorpresa en el log de Odoo:
2022-03-03 12:35:34,090 4106 DEBUG mydb odoo.api: call my.contract(13,).write({'grant_ids': [[1, 31, {'percent': 22}], [4, 32, False], [4, 33, False]]})
2022-03-03 12:35:43,773 4106 DEBUG mydb odoo.http.rpc.request: poll: None None: time:50.013s mem: 645048.0k -> 681752.0k (diff: 36704.0k)
Acerca de:
Gustavo Orrillo
Passionate about programming, he has implemented Odoo for different types of businesses since 2010. In Moldeo Interactive he is a founding Partner and Programmer; In addition to writing on the Blog about different topics related to the developments he makes.