ci: start extensive benchmark testing (execution)

[wellwelwel]

Related:

• Improve benchmarks #926

---

Check the #927 (comment) to see what's going on 💡

[github-actions]

🎖️ Benchmarks

🏃🏻‍♀️ 1/4 Execution Tests

Note

Focuses solely in execution, using a simple assert(true) or assert(false) from Node.js and searches for files in four levels of depth.

• success: a suite of 5 tests that will pass.
• failure: a suite of 5 tests that will fail.
• balanced: a suite of 10 tests where 5 tests will fail and 5 tests will pass.

See Results

---

🃏 Jest

• success

  🐷 Poku (2deb916) ran
    5.29 ± 0.11 times faster than jest

See commands

source	node --experimental-vm-modules ./node_modules/jest/bin/jest.js "./test/execution/success/jest"
poku	node ./node_modules/poku/lib/bin/index.js "./test/execution/success/poku"

• failure

  🐷 Poku (2deb916) ran
    5.44 ± 0.11 times faster than jest

See commands

source	node --experimental-vm-modules ./node_modules/jest/bin/jest.js "./test/execution/failure/jest"
poku	node ./node_modules/poku/lib/bin/index.js "./test/execution/failure/poku"

• balanced

  🐷 Poku (2deb916) ran
    4.30 ± 0.07 times faster than jest

See commands

source	node --experimental-vm-modules ./node_modules/jest/bin/jest.js "./test/execution/balanced/jest"
poku	node ./node_modules/poku/lib/bin/index.js "./test/execution/balanced/poku"

---

⚡️ Vitest

• success

  🐷 Poku (2deb916) ran
    4.69 ± 0.15 times faster than vitest

See commands

source	node ./node_modules/vitest/vitest.mjs run "./test/execution/success/vitest"
poku	node ./node_modules/poku/lib/bin/index.js "./test/execution/success/poku"

• failure

  🐷 Poku (2deb916) ran
    4.68 ± 0.14 times faster than vitest

See commands

source	node ./node_modules/vitest/vitest.mjs run "./test/execution/failure/vitest"
poku	node ./node_modules/poku/lib/bin/index.js "./test/execution/failure/poku"

• balanced

  🐷 Poku (2deb916) ran
    4.44 ± 0.11 times faster than vitest

See commands

source	node ./node_modules/vitest/vitest.mjs run "./test/execution/balanced/vitest"
poku	node ./node_modules/poku/lib/bin/index.js "./test/execution/balanced/poku"

---

☕️ Mocha

• success

  🐷 Poku (2deb916) ran
    1.85 ± 0.07 times faster than mocha

See commands

source	node ./node_modules/mocha/bin/mocha.js --parallel "./test/execution/success/mocha/**"
poku	node ./node_modules/poku/lib/bin/index.js "./test/execution/success/poku"

• failure

  🐷 Poku (2deb916) ran
    1.89 ± 0.07 times faster than mocha

See commands

source	node ./node_modules/mocha/bin/mocha.js --parallel "./test/execution/failure/mocha/**"
poku	node ./node_modules/poku/lib/bin/index.js "./test/execution/failure/poku"

• balanced

  🐷 Poku (2deb916) ran
    1.16 ± 0.03 times faster than mocha

See commands

source	node ./node_modules/mocha/bin/mocha.js --parallel "./test/execution/balanced/mocha/**"
poku	node ./node_modules/poku/lib/bin/index.js "./test/execution/balanced/poku"

---

🐢 Node.js (built-in)

• success

  node ran
    1.14 ± 0.06 times faster than 🐷 Poku (2deb916)

See commands

source	node --test "./test/execution/success/node/**/**.spec.js"
poku	node ./node_modules/poku/lib/bin/index.js "./test/execution/success/poku"

• failure

  node ran
    1.07 ± 0.04 times faster than 🐷 Poku (2deb916)

See commands

source	node --test "./test/execution/failure/node/**/**.spec.js"
poku	node ./node_modules/poku/lib/bin/index.js "./test/execution/failure/poku"

• balanced

  node ran
    1.10 ± 0.03 times faster than 🐷 Poku (2deb916)

See commands

source	node --test "./test/execution/balanced/node/**/**.spec.js"
poku	node ./node_modules/poku/lib/bin/index.js "./test/execution/balanced/poku"

---

Important

Please take into consideration that benchmarks do not indicate the competitiveness of one over the other; rather, they serve as a metric to monitor and objectively assess the current performance state of the project.