2.1 KiB
threads
There are multiple thread pools used in mergerfs to provide parallel behaviors.
read-thread-count
Defaults to 0
The number of threads used to read messages from the kernel. If used
alone processing will be done on the same thread. If
process-thread-count is enabled then this thread pool will read
messages and the process thread pool will do the work. This can
increase how much mergerfs can process at one time but may reduce
throughput.
read-thread-count=NwhereN>0: Create a thread pool ofNthreads.read-thread-count=NwhereN<0: Create a thread pool ofCPUCount / -Nthreads.read-thread-count=0andprocess-thread-count!=-1: Creates2read threads and number of process threads as defined below.read-thread-count=0andprocess-thread-count=-1: Creates2read threads and upto8process threads depending on the CPU core count.
process-thread-count
Defaults to -1
When enabled this sets the number of threads in the message processing pool.
process-thread-count=-1: Process thread pool is disabled.process-thread-count=0: Create a thread pool upto8process threads depending on the CPU core count.process-thread-count=NwhereN>0: Create a thread pool ofNthreads.process-thread-count=NwhereN<-1: Create a thread pool ofCPUCount / -Nthreads. Minimum of 1.
process-thread-queue-depth
Defaults to 2
Sets the depth queue for the processing thread queue per thread. Meaning if the read threads are getting requests faster than can be processed they will be queued up upto the queue depth. Despite the calculation being per thread the queue depth is shared across all in the pool.
process-thread-queue-depth=NwhereN>0: Sets the number of outstanding requests that the process thread pool can have toN * process-thread-count. If requests come in faster than can be processed and the max queue depth hit then queuing the request will block in order to limit memory growth.process-thread-queue-depth<=0: Sets the queue depth to 2. May be used in the future to set dynamically.