Safe Server Threads

As the server farm becomes larger and larger, it becomes useful to allow the vovserver to use multiple threads to handle the costly read-only services, such as listing sets of jobs or retrieving the complete list of taskers.

This capability is controlled by the parameter thread.service.max, which has a default value of 2. To completely turn off this capability, set the parameter to 0. For example:

# In policy.tcl file:  increase number of concurrent threads allowed.
set config(thread.service.max) 8

Turn Off Threads

# In policy.tcl file:  turn off completely threads.
set config(thread.service.max) 0

Recommendation on Linux Systems

Safe threads are forked versions of vovserver, which should live no more than 60 seconds. Typically, these threads need to live for only a few seconds.

If the memory footprint of the vovserver is a significant fraction of the total virtual memory on the job host, the number of threads can be increased by setting the kernel parameter vm.overcommit_memory to 1.

For example:

# Example: 
# sysctl -w vm.overcommit_memory=1

# Optional
# sysctl -w vm.overcommit_ratio=50