I am having a database with lots of account move lines , while loading the trial balance on screen report without applying ir rules , it gets load within 30 seconds or so , but if i apply record rules it takes a lots of time like 6 - 7 minutes , i think the query execution takes a lots of time !!
I have also generated odoo profile but it gives like majority parts goes to get_html method , but while debugging , majority time goes on get_lines method and the html is loaded within seconds after that .
Any idea how to optimise this or track where is the exact point of failure or issue , i even done indexing on the fields included in record rules .. but no difference , also no compute field in that.
Thanks
Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
- CRM
- e-Commerce
- Księgowość
- Zapasy
- PoS
- Projekt
- MRP
To pytanie dostało ostrzeżenie
1
Odpowiedz
1756
Widoki
Also the query has multiple union all with same conditions !! and all with applied record rule conditions.
Podoba Ci się ta dyskusja? Dołącz do niej!
Stwórz konto dzisiaj, aby cieszyć się ekskluzywnymi funkcjami i wchodzić w interakcje z naszą wspaniałą społecznością!
Zarejestruj się| Powiązane posty | Odpowiedzi | Widoki | Czynność | |
|---|---|---|---|---|
|
1
wrz 25
|
1528 | ||
|
2
lut 23
|
2706 | ||
|
1
cze 18
|
6643 | ||
|
2
cze 16
|
6688 | ||
|
0
cze 15
|
4785 |
could you share the domain applied for the rule
Niyas,
actually there are multiple record rules in there, in between 10 to 15
All for different use case , but when we go to trial balance they all get applies and makes the query so heavy !! Same conditions also applies on the general ledger but it gets printed in no time , and also i see some repeated union all statements also in the trial balance query , do you think maybe that can be a reason ??
How can i trace it like what is not working here , because the profilers are saying its the html , but i am debugging code and it takes maximum time for cr.execute !! So i am stuck here.