Django Q Documentation
Release 0.4.6are kept in memory by a single cluster. Setting this to a reasonable number, can help balance the workload and the memory overhead of each individual cluster. It can also be used to manage the loss of data manage.py qcluster 1.4.3 Process managers While you certainly can run a Django Q with a process manager like Supervisor or Circus it is not strictly necessary. The cluster has an internal sentinel that crashes. Because of the multiprocessing daemonic nature of the cluster, it is impossible for a process manager to determine the clusters health and resource usage. An example circus.ini [circus] check_delay0 码力 | 36 页 | 249.57 KB | 1 年前3
Django Q Documentation
Release 0.5.3are kept in memory by a single cluster. Setting this to a reasonable number, can help balance the workload and the memory overhead of each individual cluster. It can also be used to manage the loss of data python manage.py qcluster Process managers While you certainly can run a Django Q with a process manager like Supervisor [http://supervisord.org/] or Circus [https://circus.readthedocs.org/en/latest/] crashes. Because of the multiprocessing daemonic nature of the cluster, it is impossible for a process manager to determine the clusters health and resource usage. An example circus.ini [circus] check_delay0 码力 | 46 页 | 474.97 KB | 1 年前3
Django Q Documentation
Release 0.4.6are kept in memory by a single cluster. Setting this to a reasonable number, can help balance the workload and the memory overhead of each individual cluster. It can also be used to manage the loss of data python manage.py qcluster Process managers While you certainly can run a Django Q with a process manager like Supervisor [http://supervisord.org/] or Circus [https://circus.readthedocs.org/en/latest/] crashes. Because of the multiprocessing daemonic nature of the cluster, it is impossible for a process manager to determine the clusters health and resource usage. An example circus.ini [circus] check_delay0 码力 | 42 页 | 203.66 KB | 1 年前3
Django Q Documentation
Release 0.5.3are kept in memory by a single cluster. Setting this to a reasonable number, can help balance the workload and the memory overhead of each individual cluster. It can also be used to manage the loss of data manage.py qcluster 1.5.3 Process managers While you certainly can run a Django Q with a process manager like Supervisor or Circus it is not strictly necessary. The cluster has an internal sentinel that crashes. Because of the multiprocessing daemonic nature of the cluster, it is impossible for a process manager to determine the clusters health and resource usage. 1.5. Cluster 17 Django Q Documentation, Release0 码力 | 38 页 | 358.27 KB | 1 年前3
Django Q Documentation
Release 0.6.4are kept in memory by a single cluster. Setting this to a reasonable number, can help balance the workload and the memory overhead of each individual cluster. Defaults to workers**2. label The label used python manage.py qcluster Process managers While you certainly can run a Django Q with a process manager like Supervisor [http://supervisord.org/] or Circus [https://circus.readthedocs.org/en/latest/] crashes. Because of the multiprocessing daemonic nature of the cluster, it is impossible for a process manager to determine the clusters health and resource usage. An example circus.ini [circus] check_delay0 码力 | 53 页 | 512.86 KB | 1 年前3
Django Q Documentation
Release 0.6.4are kept in memory by a single cluster. Setting this to a reasonable number, can help balance the workload and the memory overhead of each individual cluster. Defaults to workers**2. 1.2.10 label The label manage.py qcluster 1.6.3 Process managers While you certainly can run a Django Q with a process manager like Supervisor or Circus it is not strictly necessary. The cluster has an internal sentinel that crashes. Because of the multiprocessing daemonic nature of the cluster, it is impossible for a process manager to determine the clusters health and resource usage. 1.6. Cluster 21 Django Q Documentation, Release0 码力 | 42 页 | 376.79 KB | 1 年前3
Django Q Documentation
Release 0.7.9are kept in memory by a single cluster. Setting this to a reasonable number, can help balance the workload and the memory overhead of each individual cluster. Defaults to workers**2. label The label used python manage.py qcluster Process managers While you certainly can run a Django Q with a process manager like Supervisor [http://supervisord.org/] or Circus [https://circus.readthedocs.org/en/latest/] crashes. Because of the multiprocessing daemonic nature of the cluster, it is impossible for a process manager to determine the clusters health and resource usage. An example circus.ini [circus] check_delay0 码力 | 62 页 | 514.67 KB | 1 年前3
Django Q Documentation
Release 0.7.9are kept in memory by a single cluster. Setting this to a reasonable number, can help balance the workload and the memory overhead of each individual cluster. Defaults to workers**2. 1.2.10 label The label Documentation, Release 0.7.8 1.6.3 Process managers While you certainly can run a Django Q with a process manager like Supervisor or Circus it is not strictly necessary. The cluster has an internal sentinel that crashes. Because of the multiprocessing daemonic nature of the cluster, it is impossible for a process manager to determine the clusters health and resource usage. An example circus.ini [circus] check_delay0 码力 | 50 页 | 397.77 KB | 1 年前3
Django Q Documentation
Release 0.7.13are kept in memory by a single cluster. Setting this to a reasonable number, can help balance the workload and the memory overhead of each individual cluster. Defaults to workers**2. 1.2.10 label The label manage.py qcluster 1.9.3 Process managers While you certainly can run a Django Q with a process manager like Supervisor or Circus it is not strictly necessary. The cluster has an internal sentinel that crashes. Because of the multiprocessing daemonic nature of the cluster, it is impossible for a process manager to determine the clusters health and resource usage. An example circus.ini [circus] check_delay0 码力 | 56 页 | 416.37 KB | 1 年前3
Django Q Documentation
Release 0.7.11are kept in memory by a single cluster. Setting this to a reasonable number, can help balance the workload and the memory overhead of each individual cluster. Defaults to workers**2. 1.2.10 label The label manage.py qcluster 1.9.3 Process managers While you certainly can run a Django Q with a process manager like Supervisor or Circus it is not strictly necessary. The cluster has an internal sentinel that crashes. Because of the multiprocessing daemonic nature of the cluster, it is impossible for a process manager to determine the clusters health and resource usage. 32 Chapter 1. Features Django Q Documentation0 码力 | 54 页 | 412.45 KB | 1 年前3
共 81 条
- 1
- 2
- 3
- 4
- 5
- 6
- 9













