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 Granian 1.7.5, tested it with both Django and Quart under asginl and asgi modes respectively. The Python process under Granian seems to increase in RAM usage over time, most noticeably if the Python application is returning large responses like files.
Here's a graph showing the problem, this before when I was running with 1.7.5 and then after I downgraded back to 1.6.4. The large downspikes in memory usage on the left side is Kubernetes restarting the workers.
Git bisected the issue to this commit here 0741845
Thank you for this project!
The text was updated successfully, but these errors were encountered:
No, it's probably just some bad code in ffi calls.
Gonna push a patch release later with --task-impl set to asyncio by default; at least until I figure out what's wrong.
gi0baro
changed the title
Memory leak, responses seem to remain in memory
Memory leak with rust task impl
Jan 29, 2025
Using Granian 1.7.5, tested it with both Django and Quart under asginl and asgi modes respectively. The Python process under Granian seems to increase in RAM usage over time, most noticeably if the Python application is returning large responses like files.
Here's a small example using Quart
and a small example with Django (generate a new project and then throw this into the root
urls.py
)Here's a graph showing the problem, this before when I was running with 1.7.5 and then after I downgraded back to 1.6.4. The large downspikes in memory usage on the left side is Kubernetes restarting the workers.
Git bisected the issue to this commit here 0741845
Thank you for this project!
The text was updated successfully, but these errors were encountered: