diff options
Diffstat (limited to '_sources/settings_file.txt')
| -rw-r--r-- | _sources/settings_file.txt | 51 |
1 files changed, 51 insertions, 0 deletions
diff --git a/_sources/settings_file.txt b/_sources/settings_file.txt new file mode 100644 index 0000000..b0bc36c --- /dev/null +++ b/_sources/settings_file.txt | |||
| @@ -0,0 +1,51 @@ | |||
| 1 | ######## | ||
| 2 | Settings | ||
| 3 | ######## | ||
| 4 | EventMQ uses a standard INI style config file found at ``/etc/eventmq.conf``. | ||
| 5 | |||
| 6 | ****** | ||
| 7 | Router | ||
| 8 | ****** | ||
| 9 | |||
| 10 | ********* | ||
| 11 | Scheduler | ||
| 12 | ********* | ||
| 13 | |||
| 14 | *********** | ||
| 15 | Job Manager | ||
| 16 | *********** | ||
| 17 | |||
| 18 | concurrent_jobs | ||
| 19 | =============== | ||
| 20 | Default: 4 | ||
| 21 | |||
| 22 | This is the number of concurrent jobs the indiviudal job manager should execute | ||
| 23 | at a time. If you are using the multiprocess or threading model this number | ||
| 24 | becomes important as you will want to control the load on your server. If the | ||
| 25 | load equals the number of cores on the server, processes will begin waiting for | ||
| 26 | cpu cycles and things will begin to slow down. | ||
| 27 | |||
| 28 | A safe number to choose if your jobs block a lot would be (2 * cores). If your | ||
| 29 | jobs are cpu intensive you will want to set this number to the number of cores | ||
| 30 | you have or (cores - 1) to leave cycles for the os and other processes. This is | ||
| 31 | something that will have to be tuned based on the jobs that are | ||
| 32 | running. Grouping similar jobs in named queues will help you tune this number. | ||
| 33 | |||
| 34 | queues | ||
| 35 | ====== | ||
| 36 | Default: (10, default) | ||
| 37 | |||
| 38 | Semi-colon seperated list of queues to process jobs for with thier | ||
| 39 | weights. Example: ``queues=(10, data_process); (15, email)``. With these | ||
| 40 | weights and the ``CONCURRENT_JOBS`` setting, you should be able to tune managers | ||
| 41 | running jobs locally pretty efficiently. If you have a larger box with a weight | ||
| 42 | of 50 on q1 and 8 concurrent jobs and a smaller box with a weight 30 and 4 | ||
| 43 | concurrent jobs, the q1 jobs will be sent to the large box until it is no longer | ||
| 44 | accepting jobs. At this point jobs will start to be sent to the next highest | ||
| 45 | number until the large box is ready to accept another q1 job. | ||
| 46 | |||
| 47 | .. note:: | ||
| 48 | |||
| 49 | It is recommended that you have some workers listening for jobs on your | ||
| 50 | default queue so that anything that is not explicitly assigned will still be | ||
| 51 | run. | ||