node-resque - npm Package Compare versions

Comparing version 0.10.2 to 0.11.0

index.js

 exports.connection     = require(__dirname + "/lib/connection.js").connection;
 exports.queue          = require(__dirname + "/lib/queue.js").queue;
 exports.worker         = require(__dirname + "/lib/worker.js").worker;
+exports.multiWorker    = require(__dirname + "/lib/multiWorker.js").multiWorker;
 exports.scheduler      = require(__dirname + "/lib/scheduler.js").scheduler;

package.json

@@ -5,3 +5,3 @@ {
   "description": "an opinionated implementation of resque in node",
-  "version": "0.10.2",
+  "version": "0.11.0",
   "homepage": "http://github.com/taskrabbit/node-resque",
@@ -8,0 +8,0 @@ "repository": {

readme.md

@@ -271,3 +271,45 @@ # node-resque
 
+## Multi Worker
+
+node-resque provides a wrapper around the `worker` object which will auto-scale the number of resque workers.  This will process more than one job at a time as long as there is idle CPU within the event loop.  For example, if you have a slow job that sends email via SMTP (with low rendering overhead), we can process many jobs at a time, but if you have a math-heavy operation, we'll stick to 1.  The `multiWorker` handles this by spawngning more and more node-resque workers and managing the pool.  
+
+```javascript
+var NR = require(__dirname + "/../index.js");
+
+var connectionDetails = {
+  package:   "redis",
+  host:      "127.0.0.1",
+  password:  ""
+}
+
+var multiWorker = new NR.multiWorker({
+  connection: connectionDetails, 
+  queues: ['slowQueue'],
+  minWorkers:        1,
+  maxWorkers:        100,
+  checkTimeout:      1000,
+  maxEventLoopDelay: 10,  
+}, jobs, function(){
+
+  // normal worker emitters
+  multiWorker.on('start',             function(workerId){                      console.log("worker["+workerId+"] started"); })
+  multiWorker.on('end',               function(workerId){                      console.log("worker["+workerId+"] ended"); })
+  multiWorker.on('cleaning_worker',   function(workerId, worker, pid){         console.log("cleaning old worker " + worker); })
+  multiWorker.on('poll',              function(workerId, queue){               console.log("worker["+workerId+"] polling " + queue); })
+  multiWorker.on('job',               function(workerId, queue, job){          console.log("worker["+workerId+"] working job " + queue + " " + JSON.stringify(job)); })
+  multiWorker.on('reEnqueue',         function(workerId, queue, job, plugin){  console.log("worker["+workerId+"] reEnqueue job (" + plugin + ") " + queue + " " + JSON.stringify(job)); })
+  multiWorker.on('success',           function(workerId, queue, job, result){  console.log("worker["+workerId+"] job success " + queue + " " + JSON.stringify(job) + " >> " + result); })
+  multiWorker.on('failure',           function(workerId, queue, job, failure){ console.log("worker["+workerId+"] job failure " + queue + " " + JSON.stringify(job) + " >> " + failure); })
+  multiWorker.on('error',             function(workerId, queue, job, error){   console.log("worker["+workerId+"] error " + queue + " " + JSON.stringify(job) + " >> " + error); })
+  multiWorker.on('pause',             function(workerId){                      console.log("worker["+workerId+"] paused"); })
+  
+  // multiWorker emitters
+  multiWorker.on('internalError',     function(error){                         console.log(error); })
+  multiWorker.on('miltiWorkerAction', function(verb, delay){                   console.log("*** checked for worker status: " + verb + " (event loop delay: " + delay + "ms)"); })
+
+  multiWorker.start();
+});
+```
+
 ## Acknowledgments
 Most of this code was inspired by / stolen from [coffee-resque](https://npmjs.org/package/coffee-resque) and [coffee-resque-scheduler](https://github.com/leeadkins/coffee-resque-scheduler).  Thanks!

New alerts

Dynamic require

Supply chain risk

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

124398

increased by6.62%

Number of package files

38

increased by5.56%

Lines of code

2792

increased by4.41%

Number of lines in readme file

315

increased by15.38%

Worsened metrics

Number of low supply chain risk alerts

36

increased by9.09%

No dependency changes