{{ lang.t("Set the maximum number of concurrent system tasks that may run simultaneously. JetBackup utilizes one fork per system task on the server. (Maximum value of 10)") }}
{{lang.t("NOTE: Higher value doesn't necessarily mean higher performance, we recommend 1 task per server CPU core, but no more than 5 for daily usage, and 10 for restoring in a disaster recovery mode.")}}

{{ lang.t("Set the maximum number of concurrent restore/download/reindex tasks that may run simultaneously. JetBackup utilizes one fork per restore/download task on the server. (Maximum value of 10)") }}
{{lang.t("NOTE: Higher value doesn't necessarily mean higher performance, we recommend 1 task per server CPU core, but no more than 5 for daily usage, and 10 for restoring in a disaster recovery mode.")}}

{{ lang.t("Set the maximum number of concurrent backup/clone tasks that may run simultaneously. JetBackup utilizes one fork per Directories Backup Job or one fork per account on an Account Backup/Clone Job. (Maximum value of 10)") }}
{{lang.t("NOTE: Higher value doesn't necessarily mean higher performance, we recommend 1 task per server CPU core, but no more than 5. You also need to consider limiting CPU usage (200% is a reasonable limit).")}}

{{ lang.t("Set the maximum time a backup/clone fork can run in hours. It will automatically abort once it reaches the set TTL.") }}

{{ lang.t("Set the time that backup cleanup & integrity check should run in days. (Minimum value of 1 and Maximum value of 90)") }}

{{ lang.t("Select the number of downloads that you permit to keep for each account.") }}

{{ lang.t("Manage Queue Priority Groups") }}

{{ lang.t("Here you can manage all of the queue processes priority groups.") }}

{{ lang.t("Set the queue priority group assigned to a directory in relation to account download & restore queue priority groups.") }} {{const.DOCS_ADMIN_URL}}/settings.html#performance

{{ lang.t("MySQL / MariaDB Settings") }}

{{ lang.t("The maximum packet length to send to or receive from server") }}

{{ lang.t("Continue even if we get an SQL error") }}

{{ lang.t("Same as --add-drop-table, --add-locks, --create-options, --skip-opt.") }}

{{ lang.t("This option enables control over global transaction ID (GTID) information written to the dump file, by indicating whether to add a SET @@GLOBAL.gtid_purged statement to the output. This option may also cause SET @@SESSION.sql_log_bin=0 to be written to the output that disables binary logging while the dump file is being reloaded.SET @@SESSION.sql_log_bin=0 and @@GLOBAL.gtid_purged statements require SUPER privileges which may be unavailable in environments such as Amazon RDS.") }}

{{ lang.t("Unless you have a specific requirement to change this option, we recommend keeping the DEFAULT or OFF values for the best performance and reliability.") }}

{{ lang.t("NOTE: MariaDB and MySQL have different implementations of GTID which aren't compatible. If using MariaDB, only the DEFAULT option should be selected.") }}