-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
fix: log memory usage for requests based on configured memory limit #57590
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Simon L. <szaimen@e.mail.de>
e00ae8f to
287fe12
Compare
ChristophWurst
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice
|
CI failure is unrelated afaics |
|
|
||
| // Check if a memory limit is configured and can be retrieved and determine log level | ||
| if ($memoryLimit !== null && $memoryLimit !== -1) { | ||
| $logLevel = match (true) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| $logLevel = match (true) { | |
| $memoryLimit = min(512_000_000, $memoryLimit); | |
| $logLevel = match (true) { |
I'd prefer this to be capped to 512M. We always want to log things when they are above ~300M, and not skip them because the developer uses 2G locally
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is how this is currently implemented. However we get a lot of complaints by admins and users. See the issue I am trying to fix: #52997
Signed-off-by: Simon L. <szaimen@e.mail.de>
9d61e68 to
45d3c64
Compare
Uh oh!
There was an error while loading. Please reload this page.