Maybe you should review the 'high calculation/high plotly' pages for memory
usage?
As the 'OOM killer' kicked in, it looks like the process is using too much
memory.
One thing to verify this is to monitor the VmRSS of the processes involved
(VmRSS is one of the fields in the output when you do
While I can't provide a specific solution, it might be a better approach to
keep resource-intensive tasks separate from web2py, using a tool like
Celery. This way, these tasks can run in the background without impacting
the web server.
This is a small docx about how to put it together:
https://doc
2 matches
Mail list logo
