Configuring runners#

Overview#

The default runner QueueRunner isn't great for any serious queue throughput, and causes delays before a job gets picked up. Here's some alternatives.

You might also be interested in ways to run immediate jobs through watchers such as inotifyd.

Using Doormanfor running jobs#

Doorman is included by default, and allows for asynchronous task processing.

This requires that you are running an a unix based system, or within some kind of environment emulator such as cygwin.

In order to enable this, configure the ProcessJobQueueTask to use this backend.

---
Name: localproject
After: '#queuedjobsettings'
---
SilverStripe\Core\Injector\Injector:
  Symbiote\QueuedJobs\Services\QueuedJobService:
    properties:
      queueRunner: %$DoormanRunner

See Multi process execution in Doorman for more ways to increase concurrency in Doorman.

Using Gearmanfor running jobs#

• Make sure gearmand is installed
• Get the gearman module from https://github.com/nyeholt/silverstripe-gearman
• Create a _config/queuedjobs.yml file in your project with the following declaration

---
Name: localproject
After: '#queuedjobsettings'
---
SilverStripe\Core\Injector\Injector:
  QueueHandler:
    class: Symbiote\QueuedJobs\Services\GearmanQueueHandler

• Run the gearman worker using php gearman/gearman_runner.php in your SS root dir

This will cause all queuedjobs to trigger immediate via a gearman worker (src/workers/JobWorker.php) EXCEPT those with a StartAfter date set, for which you will STILL need the cron settings from above