[poolifier.git] / benchmarks / README.md

# Poolifier Benchmarks

Welcome to poolifier benchmarks and thanks to look into this project.

## Folder Structure

The [internal](./internal) folder contains poolifier internal benchmarks.  
The [versus-external-pools](./versus-external-pools) folder contains benchmarks versus other Node.js pools.

## Poolifier vs other pools benchmark

To compare poolifier pools performance vs other pools performance we chose to use [hyperfine](https://github.com/sharkdp/hyperfine).  
We chose to use this tool because it allows to run isolated Node.js processes so that each pool does not impact each other.  
External pools with which we compared the poolifier results:

- [piscina](https://github.com/piscinajs/piscina)
- [SUCHMOKUO/node-worker-threads-pool](https://github.com/SUCHMOKUO/node-worker-threads-pool)
- [threads.js](https://github.com/andywer/threads.js/)
- [workerpool](https://github.com/josdejong/workerpool)
- [threadwork](https://github.com/kevlened/threadwork)
- [microjob](https://github.com/wilk/microjob)

Those are our results:

- CPU Intensive task with 100k operations submitted to each pool [BENCH-100000.md](./versus-external-pools/BENCH-100000.md).

> :warning: **We would need funds to run our benchmarks more often and on Cloud VMs, please consider to sponsor this project**

## How to run benchmarks

### Internal

To run the internal benchmarks, you just need to navigate to the root of poolifier project and run `pnpm benchmark`

## Versus other pools

Read [README.md](./versus-external-pools/README.md)
Commit	Line	Data
	1	# Poolifier Benchmarks
	2
	3	Welcome to poolifier benchmarks and thanks to look into this project.
	4
	5	## Folder Structure
	6
	7	The [internal](./internal) folder contains poolifier internal benchmarks.
	8	The [versus-external-pools](./versus-external-pools) folder contains benchmarks versus other Node.js pools.
	9
	10	## Poolifier vs other pools benchmark
	11
	12	To compare poolifier pools performance vs other pools performance we chose to use [hyperfine](https://github.com/sharkdp/hyperfine).
	13	We chose to use this tool because it allows to run isolated Node.js processes so that each pool does not impact each other.
	14	External pools with which we compared the poolifier results:
	15
	16	- [piscina](https://github.com/piscinajs/piscina)
	17	- [SUCHMOKUO/node-worker-threads-pool](https://github.com/SUCHMOKUO/node-worker-threads-pool)
	18	- [threads.js](https://github.com/andywer/threads.js/)
	19	- [workerpool](https://github.com/josdejong/workerpool)
	20	- [threadwork](https://github.com/kevlened/threadwork)
	21	- [microjob](https://github.com/wilk/microjob)
	22
	23	Those are our results:
	24
	25	- CPU Intensive task with 100k operations submitted to each pool [BENCH-100000.md](./versus-external-pools/BENCH-100000.md).
	26
	27	> :warning: We would need funds to run our benchmarks more often and on Cloud VMs, please consider to sponsor this project
	28
	29	## How to run benchmarks
	30
	31	### Internal
	32
	33	To run the internal benchmarks, you just need to navigate to the root of poolifier project and run `pnpm benchmark`
	34
	35	## Versus other pools
	36
	37	Read [README.md](./versus-external-pools/README.md)