On Tuesday, July 28, 2020 at 1:53:18 AM UTC-7, Jose C wrote: > > Just FYI, the web2py book states: > > Try to avoid web2py cron, and use a background process instead. web2py >> cron can start too many Python instances and cause excessive memory >> usage. >> > > Using scheduler means an additional long running process using up memory > to monitor and manage the scheduler. > > This is a problem for you? I've had my scheduler running on AWS and Postgres for months without issue. I actually have a second scheduler running in sqlite3 on the same machine. No issue.
> I'd recommend using your system crontab to run any background processes. > This can be invoked within the full web2py environment (if needed) from > crontab as follows: > > # Runs every 5 minutes. > */5 * * * * python3 /path/to/web2py.py --no_gui --no-banner -S > <web2py_app_name> -M -R /path/to/process/background_process.py > > HTH, > > Things that aren't python are better run via system cron, but the scheduler does a fine job for application-related pythonic work. /dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/0daf8ef8-02e5-411d-98de-f90793442b38o%40googlegroups.com.
