Socket
Socket
Sign inDemoInstall

pararr

Package Overview
Dependencies
0
Maintainers
1
Versions
2
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

    pararr

Parallel computing for Node


Version published
Maintainers
1
Install size
37.5 kB
Created

Readme

Source

#Pararr.js - Parallel computing for Node

Modern multicore systems can process lots of data in parallel but writing parallel code can be tricky. Pararr.js provides an easy-to-use API for parallel computing in Node and parallel implementations of standard array functions like map or filter that utilize all available cores in the system when calculating their result.

##Installation npm install pararr

##Usage var p = require('pararr'),

    arr = [1,2,3,4,5,6,7,8,9,10],
	
	// Inperformant primality check
	isPrime = function(a) {
		var i;
		if (a <= 2) {
			return true;
		}
		for (i = Math.ceil(Math.sqrt(a)) ; i > 1; i--) {
			if (a % i === 0) {
				return false;
			}
		}
		return true;
	};

	
// Parallel filter
p.filter(arr, isPrime, function(err, res) {
    console.log('Parallel filter returned: ' + res);
    
    p.destroy(); //Cleanup
});	

Outputs:

Parallel filter returned: 1,2,3,5,7

See benchmark.js for more examples

##Demo / Benchmark To run demo:

node demo.js

To run benchmark:

node benchmark.js

##API

  • init
  • exec
  • parallel
  • map
  • filter
  • sort
  • destroy

##Considerations Pararr creates a V8 instance for each CPU core which has an effect memory consumption and startup time. When a calculation is dispatched to a worker the function and its data is copied and sent to the corresponding instance which causes an shorter or longer delay depending mainly on the data volume. Generally speaking we can benefit from parallelization in this form when data volumes are small and CPU cycles is a bottleneck.

For array functions such as map or filter the partitioning of the input data and transporting it to the workers takes time (O(n)), so if the iterator function is fast (O(1)) parallelization won't have a positive effect on performance. However, if the iterator function is slow we can benefit greatly from parallel processing. See benchmark.js for examples of good and bad use cases.

##Functions

### init()

Initializes Pararr. If this function isn't called, Pararr will be initialized lazily


### exec( func(par), par, callback(err, result) )

Execute function func with parameter par when a CPU becomes free and return the result in callback.

Arguments

func     {Function} Function to be executed
par      {Object|Number|String} parameter with which func will be called
callback {Function} Callback called when finished.

### parallel( funcs, callback(result) )

Execute a number of functions in parallel. When all functions have returned callback returns an array containing the results.

Arguments

funcs    {Array} Array of functions to be executed. Each elements is an object containing a function *func* and a parameter *par*
callback {Function} Callback called when finished. Results are returned in form of an array with the same indexing as funcs.

### map( arr, iter(a), callback(err, result) )

Apply a function to each element in an array

Arguments

arr      {Array} input array
iter     {Function} Iterator function (Must be a pure function)
callback {Function} Callback called when finished.

### filter( arr, iter(a), callback(err, result) )

Filter an an array

Arguments

arr      {Array} input array
iter     {Function} Filter function that returns true or false (Must be a pure function)
callback {Function} Callback called when finished.

### sort( arr, comp(a,b), callback(err, result) )

Sort the array arr

Arguments

arr      {Array} input array
comp     {Function} Comparator with the same interface as for native sort
callback {Function} Callback called when finished.

### destroy()

Free all resources (kill workers)


##Tests Run tests with nodeunit:

 nodeunit test

##Roadmap

  • Implement heuristic to autumatically detect whether parallel execution will be faster

##License (MIT License)

Copyright (c) 2012 Aron Kornhall

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Keywords

FAQs

Last updated on 20 Mar 2012

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc