microjob | tiny wrapper for turning Node | Runtime Evironment library

by wilk TypeScript Version: 0.7.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | microjob Summary

microjob is a TypeScript library typically used in Server, Runtime Evironment, Nodejs applications. microjob has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

Microjob is a tiny wrapper for Node.js threads and is intended to perform heavy CPU loads using anonymous functions. ~~So, Microjob treats Node.js threads as temporary working units: if you need to spawn a long-living thread, then you should use the default API.~~. From version v0.1.0 microjob uses a Worker Pool .

Support

Quality

Security

License

Reuse

Support

microjob has a medium active ecosystem.

It has 1972 star(s) with 55 fork(s). There are 32 watchers for this library.

It had no major release in the last 12 months.

There are 7 open issues and 40 have been closed. On average issues are closed in 39 days. There are 9 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of microjob is 0.7.0

Quality

microjob has no bugs reported.

Security

microjob has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

microjob is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

microjob releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of microjob

Get all kandi verified functions for this library.

microjob Key Features

No Key Features are available at this moment for microjob.

microjob Examples and Code Snippets

No Code Snippets are available at this moment for microjob.

Community Discussions

Trending Discussions on microjob

Is there a way to force terminate a worker thread in node.js?

multiple threads vs fork process in NodeJS

QUESTION

Is there a way to force terminate a worker thread in node.js?

Asked 2021-Feb-07 at 06:16

I was looking around for my question but to no avail. I wanted to know if there was a way to force a worker to terminate a worker thread even if its task hadn't been completed. I have some code in there that calls itself if it somehow fails, which is intentional even though it might be bad code practice. I tried using libraries such as microjob and threads, but those didn't have what I wanted. Here is what I tried to do with threads but didn't work:

...

ANSWER

Answered 2021-Feb-07 at 06:16

I have solved my issue by using clusters in Node.JS, which uses the child_process to run the workers.

Here is a link to the documentation if anyone needs it: https://nodejs.org/api/cluster.html

Source https://stackoverflow.com/questions/66021137

QUESTION

multiple threads vs fork process in NodeJS

Asked 2019-Jul-08 at 07:22

I'm trying to find a better way to run some cpu bound tasks using NodeJS. There are 2 options as I know, fork processes and worker threads. So I have ran a benchmark between them and found out that fork process is faster.

So, I have some questions here:

Why is the fork process method faster?
Are the worker threads useless? Or what are the worker threads advantages, consumes less cpu/memory?

I'm running the code on MacOS(2.2 GHz Intel Core i7, 16 GB 1600 MHz DDR3) using node v10.15.3

the benchmark code is in my gist:

threads pool library microjob and process pool library node-worker-farm are used in my code as you can see. The running cmd is : node --experimental-worker benchmark.js

...

ANSWER

Answered 2019-Jul-08 at 07:22

I think @gireeshpunathil's comment from https://github.com/nodejs/help/issues/1920 can help a lot:

there is no single formulae that computes which method will be faster. It depends on a number of parameters:

the running time of the job itself

the interaction of the job with the spawning code

the machine characteristics, specifically cpu, memory and scheduling

the fork uses native fork and exec, that is heavy-weight than thread creation. fork creates a new node instance with new v8, isolate, libuv etc. worker does not create new node instance. forked process uses IPC channel to talk to the forking process, if needed. workers use in-memory buffers.

So:

if the execution time of the microjob is too small compared to the process creation, worker method will be faster.

if the job communicates with the driver, the frequency of communication and the cost of communication will decide the winner

if the job runs as long independent piece of code with no interaction, fork method will eventually prove faster (I think that
is happening here)