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
We noticed that you recently pushed an update where you changed the Debian version by 2 major releases. (from 10 to 12). This caused us some issue in our AWS infrastructure but most noticeable is the much higher load that the latest digest ( sha256:bc07654603775b9843693f57645b521bc4e9477b7afe74dc62187aa1a247a25e ) has caused.
The traffic was almost identical during our before and after tests.
Reverting to the older revision through AWS with the older digest (sha256:1011fe6b522e8dffdfbba8548705affb2d0258c2248f08e8a33f6af54f7dac75) solved the problem.
Here is a graph demonstrating the issue:
The text was updated successfully, but these errors were encountered:
Yes, that update was necessary as the official PHP images based on buster aren't receiving updated PHP versions anymore. Therefore we needed to migrate to get the latest security updates.
If you can investigate in detail which process is causing the load => nginx, php, etc. maybe we can do something about it.
Hello,
We noticed that you recently pushed an update where you changed the Debian version by 2 major releases. (from 10 to 12). This caused us some issue in our AWS infrastructure but most noticeable is the much higher load that the latest digest ( sha256:bc07654603775b9843693f57645b521bc4e9477b7afe74dc62187aa1a247a25e ) has caused.
The traffic was almost identical during our before and after tests.
Reverting to the older revision through AWS with the older digest (sha256:1011fe6b522e8dffdfbba8548705affb2d0258c2248f08e8a33f6af54f7dac75) solved the problem.
Here is a graph demonstrating the issue:
The text was updated successfully, but these errors were encountered: