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