You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a site with ~2000 "products" entries in a collection, When I flush the app cache & refresh the stache (clear + warm)... The first page load of a template listing products (with pagination and showing "only 16" products) needs between 3 and 6 Go of RAM.
3 Go when I remove some partial doing some apparently lite stuff (ie: checking if a value exist in session and display static html if so) and 6 GO when I let them in place... That's a huge gap to me, even the first 3GO are a LOOOT to display 16 products...
On the 2nd page load, it only takes ~200 Mo of RAM. (No caching strategy enabled, and using local file as cache storage engine)
Also, what's strange is : when I clear all the app cache (+ stache refresh), and load first another page (like the home page where no products are displayed), it takes ~200 Mo of RAM for this first page, and then load the product listing template , it also takes ~200Mo of RAM.
One hypothesis (ie : Without doing code diving) about what could explain that is ... when doing some querying with an freshly emptied cache + warmed stache..., some cached items are created on the fly , but cannot be used immediately (for instance if inside a loop or something) and have to wait until the request is done ... to be usable... (for instance it's like if if cached items are put in a queue and really written on the disk at the end of the request ...). Or ... of course the reason could be something else ... ;)
But to me, needing many GO of ram on first page load and then only few hundreds, whereas the stache is warm does not smell good... what do you think ?
How to reproduce
can share a private project with core team if needed...
Bug description
On a site with ~2000 "products" entries in a collection, When I flush the app cache & refresh the stache (clear + warm)... The first page load of a template listing products (with pagination and showing "only 16" products) needs between 3 and 6 Go of RAM.
3 Go when I remove some partial doing some apparently lite stuff (ie: checking if a value exist in session and display static html if so) and 6 GO when I let them in place... That's a huge gap to me, even the first 3GO are a LOOOT to display 16 products...
On the 2nd page load, it only takes ~200 Mo of RAM. (No caching strategy enabled, and using local file as cache storage engine)
Also, what's strange is : when I clear all the app cache (+ stache refresh), and load first another page (like the home page where no products are displayed), it takes ~200 Mo of RAM for this first page, and then load the product listing template , it also takes ~200Mo of RAM.
One hypothesis (ie : Without doing code diving) about what could explain that is ... when doing some querying with an freshly emptied cache + warmed stache..., some cached items are created on the fly , but cannot be used immediately (for instance if inside a loop or something) and have to wait until the request is done ... to be usable... (for instance it's like if if cached items are put in a queue and really written on the disk at the end of the request ...). Or ... of course the reason could be something else ... ;)
But to me, needing many GO of ram on first page load and then only few hundreds, whereas the stache is warm does not smell good... what do you think ?
How to reproduce
can share a private project with core team if needed...
Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered: