This page is for system administrators
This page presents some options of the launcher script for tuning the parameters of the application components.
Performance and tuning
This project uses components based on popular projects. This documentation is not aimed to compare the performance while tuning the component parameters. For more information about their tuning, please refer to the related documentations.
The application is architectured as follows:
- Scheduling: APScheduler
- Web server: Tornado
- Web frontend: Backbone.js
- Backend DB: SQLite, MySQL or PostgreSQL
- Reverse proxy: mitmproxy
Application's options are organized per component. You can see it by invoking
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
The server can be run locally or not and its basic parameters, host IP address and port, are tunable. You can also tune the location where it searches for job classes. Note that this last parameter is a list, meaning that
--jobs can be used multiple times to include multiple paths.
1 2 3 4 5 6 7 8 9 10
The scheduler can be tuned to send email notifications when tasks give an output. You can tune this by specifying an SMTP configuration in the INI format and one or more SMTP profiles, as defined in the SMTP configuration. These profiles are the section titles of the INI configuration.
1 2 3 4 5 6 7
SMTP INI configuration fields
The format supports 7 fields, like shown in the example below.
1 2 3 4 5 6 7 8
For the sake of simplicity, a template configuration is provided in the
conf folder of the project.
Note that, for the
security field, using a default port sets it to the appropriate value such as in the following list. Setting this value is thus, in most cases, not required.
Thanks to NdScheduler, 3 different classical backends can be selected: SQLite, MySQL and PostgreSQL. The table names can all be tuned for a better flexibility into a production DBMS.
1 2 3 4 5 6 7 8 9 10 11 12 13
The scheduler has multiple parameters that can be tuned as the timezone or coalescing missed job executions. It can limit concurrent executing instances of a same job and applies a grace time for job misfire for preventing the scheduler from being overwhelmed.
1 2 3 4 5 6 7 8 9 10 11
The Web server has only one option for tuning its number of workers.
1 2 3 4 5
The reverse authentication proxy is started as a separate process just before starting the scheduling server and stops right after this last one. It can be tuned with a certificate (then avoiding annoying warning messages or blocking due to an unregistered certificate) and a
.htpasswd credentials file (beware to configure it with relevant permissions).
1 2 3 4 5 6 7 8