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
It seems that calling multiple queries in succession (about 10-50, (Gatsby build)) craft/php begins to over use its allocated memory. I allocate craft 256M of memory (to php) as indicated in my docker file.
and I also have limited the docker container to 300MB of ram using docker-compose mem_limit
After starting a build (Gatsby begins to hit the endpoint with queries) the craft sever quickly hits the memory limit imposed on it by docker (ignoring the memory limit imposed by php) which results in an 500 error (Out of memory, on the server logs).
The server that I run this in production is a small 1gb ram DO droplet with two replicated environments (staging, production) hence the strict ram restrictions.
Is there any way to either disable caching or reduce its impact when running consecutive queries?
Any help will be appreciated.
Thank you in advance!
The text was updated successfully, but these errors were encountered:
It seems that calling multiple queries in succession (about 10-50, (Gatsby build)) craft/php begins to over use its allocated memory. I allocate craft 256M of memory (to php) as indicated in my docker file.
and I also have limited the docker container to 300MB of ram using docker-compose
mem_limit
After starting a build (Gatsby begins to hit the endpoint with queries) the craft sever quickly hits the memory limit imposed on it by docker (ignoring the memory limit imposed by php) which results in an 500 error (Out of memory, on the server logs).
The server that I run this in production is a small 1gb ram DO droplet with two replicated environments (staging, production) hence the strict ram restrictions.
Is there any way to either disable caching or reduce its impact when running consecutive queries?
Any help will be appreciated.
Thank you in advance!
The text was updated successfully, but these errors were encountered: