- Mailing Lists
- Contributors
- Re: multi company: how many companies is too many?
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
Re: multi company: how many companies is too many?
Hi,
Record rules make little difference, neither does properties in my experience. The one that can get you if you have a lot of products or customers is cost / pricelist / payment term lookups that table can get slow but a set of partial index resolves those (take care of the NULL case in each one). But you see that issue with as few as 1 company, just obviously the problem multiplies.
What can make a difference is postgres performance due to query execution plans on weirdly shaped queries due to the distribution of company_ids in what are naturally much larger tables. You can get some truly awful query planning. However again it is really just a subset of the large data issues.
In general the standard mitigations, if you have 1 large company and lots of little ones you might do a partial on the large and a partial on everything but the large. You may have to build a lot of composites with company_id as well (I'm not sure postgres optimizes the NOT NULL attribute when ORM searches for NULL companies even when required - such a simple optimization they could do).
So I guess unlike Pedro, I see issues at 10 companies, but wildly different data distributions and the largest table at 50,000,000 lines. Although usually the worst issues are reserved for enterprise reports which actually access relatively small tables, say 5m records or less, like reconcile tables, but they are date and company dependent and in big joins.
On Tue, May 10, 2022 at 9:52 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
We have one with 89 without a performance penalty. Maybe the problem is some specific unoptimized rule/s?Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Graeme Gellatly - 11:30 - 10 May 2022
Reference
-
multi company: how many companies is too many?
What is the largest number of companies you ever ran in a single (recent version) odoo instance? When does the performance start to degrade because of the record rules or company properties? -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
by Alexandre Fayolle - 11:46 - 10 May 2022