- Mailing Lists
- Contributors
- Re: initialization of qweb template caches on website
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: initialization of qweb template caches on website
Re: initialization of qweb template caches on website
Re: initialization of qweb template caches on website
This is an interesting subject, as it's kind of hard to find a sweet spot.
- If you have a high amount of workers, restarting or redeploying new changes make things hellish slow.
- Mixed setups (multiprocess for the backend + multithread for the website) make things better; but it depends on the load and amount of online visitors that you could have at the same time.
- Nginx caching and CDNs are your friends. Don't be afraid of caching /web/content, but do not cache it for excessive times.
Hello, A customer (odoo 12.0) here is facing a performance issue related to qweb templates on the website. The first time a worker serves these, we get terrible performance. I suspect we are not the only ones facing this. Using an external service to GET /shop for instance on a regular basis sort of alleviates this, but this is really unelegant. Is there a killer module I missed which is able to preload the cache for a number of views each time a worker is started? Or some other strategy? Thanks for your feedback -- Alexandre Fayolle Chef de Projet 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_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Gustavo Valverde Chief Technology Officer M (829) 686 8270 D (829) 956 5191 ext. 202 E gustavo@iterativo.do | |
ITERATIVO SRL Roble Corporate Center, Piso 7 Rafael Augusto Sánchez 86, Piantini, Santo Domingo, R. Dominicana T (829) 956 5191| E info@iterativo.do | www.iterativo.do Member firm of ITERATIVO LLC & Progressa Corporate Group | |
Este mensaje y sus anexos pueden contener información confidencial y privilegiada con la intención de que sea utilizada por las personas u organizaciones a quienes esta dirigida, por lo que su uso es exclusivo para su destinatario. Si usted ha recibido este mensaje por error, favor de eliminarlo e informar al remitente del mensaje a través de un correo de respuesta. Si este es el caso, le notificamos que queda estrictamente prohibida la distribución o reproducción de este e-mail y/o sus anexos. iterativo no se hace responsable de las opiniones vertidas en esta comunicación que no estén acordes con su quehacer y fines, y que no se revistan de un carácter oficial.
This message and its enclosures may contain confidential and privileged information intended for the use of people and organizations to which it is directed and its use is thus limited to its addressee. If you have received this message by mistake, please eliminate it and inform the sender through a reply message. Should this be the case, you are advised that the distribution or reproduction of this e-mail and/or any attachments contained herein is strictly forbidden. iterativo is not liable for opinions expressed in this message which may not coincide with its responsibilities and purpose and which may not express official matters.

No imprimas este correo si no es necesario. Cuidemos del ambiente!
Do not print this mail if it's not necessary. Let's take care of the environment!
by Gustavo Valverde <gustavo@iterativo.do> - 03:21 - 8 Jun 2020
Reference
-
initialization of qweb template caches on website
Hello, A customer (odoo 12.0) here is facing a performance issue related to qweb templates on the website. The first time a worker serves these, we get terrible performance. I suspect we are not the only ones facing this. Using an external service to GET /shop for instance on a regular basis sort of alleviates this, but this is really unelegant. Is there a killer module I missed which is able to preload the cache for a number of views each time a worker is started? Or some other strategy? Thanks for your feedback -- Alexandre Fayolle Chef de Projet 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 - 02:21 - 8 Jun 2020