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
queue:work ignores --memory parameter #25738
Comments
This would happen if the application is down for maintenance, the workers are paused, or you are subscribing to the Looping event and return false. If neither of these scenarios match, can you tell us what |
Please provide the results of
The second value (real usage) should never exceed your --memory limit. |
Closing this issue because it's already solved, old or not relevant anymore. Feel free to reply if you're still experiencing this issue. |
Im still facing the same or similar issue. I used the --memory parameter together with supervisor and the work command like this: However, a quite big job still fails with the "Allowed memory size of 134217728 bytes exhausted (tried to allocate 5988352 bytes)". What makes me thing that the memory option does not work is the message. It says "of 134217728 byes" which is 128MB, which is the default value of the memory parameter. In the php.ini memory_limit is also set to 512M. |
@derosavage The queue limit works only between two jobs but not within your job. |
pda/pheanstalk v3.2.1
Description:
I;m running the queue:work through supervisor with the following command:
artisan queue:work --memory=100 --queue=reportProcessing --sleep=3 --tries=3
In actuality, the processes start at around 400mb (which on itself is too high).
anyway, you would expect that after one job the worker will quite, which doesn't happen.
they will never be shutdown and eventually will reach huge amount of memory.
https://i.imgur.com/2iHwSNz.png
The text was updated successfully, but these errors were encountered: