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
Using pooled connections, we upgraded from 3.9.4 to 3.11.3 and instantly saw huge memory leaks in many deployed production enviroments. See screenshots below from google cloud run where the line with the i and dotted lines marks the deployment of the libary 3.11.3. Its very clear that its the changes between 3.9.4 and 3.11.3
Screenshot of container insights in production after deployement
I downgraded to 3.9.7 and still have the memory leaks.
Rolling back to mysql 3.9.4 solves the issue
We are using typeorm but the mysql config parms are just passed down. I will write the relevant ones below;
Using pooled connections, we upgraded from 3.9.4 to 3.11.3 and instantly saw huge memory leaks in many deployed production enviroments. See screenshots below from google cloud run where the line with the i and dotted lines marks the deployment of the libary 3.11.3. Its very clear that its the changes between 3.9.4 and 3.11.3
Screenshot of container insights in production after deployement
I downgraded to 3.9.7 and still have the memory leaks.
Rolling back to mysql 3.9.4 solves the issue
We are using typeorm but the mysql config parms are just passed down. I will write the relevant ones below;
The text was updated successfully, but these errors were encountered: