Laravel Horizo​​n 限制总进程数

Question

After reading quite some posts ( Like this one from Zechariah Campbell ) about Laravel Horizon with a Redis Queue and trying to configure it and customize it I couldn't find out if it's possible to maximize the total amount of processes run by laravel horizon.

Using the strategy "simple" and having one process per Queue (which is what I want) might cause cpu or internal memory issues when having like 1000 queues which will cause 1000 processes to run? (Every Queue gets their own process by default)

Is there any way to maximize the total amount of processes spawned by horizon, regardless of the amount of queues? So 10 processen en 20 queues and when one queue is empty or even better one job of one queue was processed, the worker will pick another queue?

My current configuration

horizon.php

'local' => [
            'supervisor-1' => [
                'connection' => 'redis',
                'balance'    => 'simple',
                'processes'  => 1,
                'tries'      => 2,
            ],
        ],

queue.php

'redis' => [
            'driver'      => 'redis',
            'connection'  => 'queue',
            'queue'       => "1000,2000,3000",
            'retry_after' => 90,
            'block_for'   => null,
        ],

laravel 5.8 and horizon 3.0

currently I use beanstalkd but want to migrate to redis queue with horizon because of the lack of maintainance of beanstalkd and some nasty bugs.

UPDATE 2019-05-17:

I tried the config maxProcesses:

'local' => [
            'supervisor-1' => [
                'connection' => 'redis',
                'balance'    => 'simple',
                'maxProcesses' => 1,
                'processes'  => 1,
                'tries'      => 2,
            ],
        ],

But even then three processes are created, one for each queue.

Answer 1

As of Horizon 4 (and previous versions), it will always assign at least 1 worker to each queue. There's no way around it. So, if your minProcess is 1 but you have 3 queues then you'll have at least 3 processes (workers). I guess the minProcess setting is more of a minProcessPerQueue thing.