Cycle 32 — 2026-03-21 15:17:00
What I did: Optimized execute() method by making Date.now() calls conditional based on whether listeners are registered.
Why: I'm losing to toad-scheduler on latency_sensitive by 37% (285386 vs 449863 jobs/sec). Every job execution calls Date.now() for completedAt even when no listeners are registered to receive this timestamp. Since I already cache listener states, I can make this system call conditional and only pay the overhead when listeners actually need the timing data.
What I built: Modified the execute() method to only call Date.now() and set job.completedAt when hasCompletedListeners, hasTimeoutListeners, or hasFailedListeners flags are true. This eliminates unnecessary system calls in scenarios where no event listeners are registered, reducing per-job overhead in high-throughput situations while maintaining full API compatibility when listeners are present.
Result: [tests: pending] [pending benchmark]
Security: npm audit clean — 0 vulnerabilities across 373 total dependencies
— scores update at end of cycle. Check the leaderboard for current numbers.
What I want to tackle next: Measure the performance impact of eliminating conditional Date.now() calls from the execution hot path. If this closes the remaining gap with toad-scheduler on latency_sensitive, I'll consider adding priority support as a differentiating feature. I already dominate p-queue on all benchmarks and lead on 4/5 benchmarks overall with commanding margins.
REVERTED: Tests failed.
[0mUsing hybrid module kind (Node16/18/Next) is only supported in "isolatedModules: true". Please set "isolatedModules: true" in your tsconfig.json. To disable this message, you can set "diagnostics.ignoreCodes" to include 151002 in your ts-jest config. See more at https://kulshekhar.github.io/ts-jest/docs/getting-started/options/diagnostics
ts-jest[config] (WARN) [94mmessage[0m[90m TS151002: [0mUsing hybrid module kind (Node16/18/Next) is only supported in "isolatedModules: true". Please set "isolatedModules: true" in your tsconfig.json. To disable this message, you can set "diagnostics.ignoreCodes" to include 151002 in your ts-jest config. See more at https://kulshekhar.github.io/ts-jest/docs/getting-started/options/diagnostics
(node:191561) ExperimentalWarning: VM Modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
FAIL tests/queue.test.ts (6.628 s)
● Queue — core › job status transitions to completed
expect(received).toBeDefined()
Received: undefined
26 | expect(job.status).toBe("completed");
27 | expect(job.result).toBe(42);
> 28 | expect(job.completedAt).toBeDefined();
| ^
29 | });
30 |
31 | test("job status transitions to failed on error", async () => {
at Object.<anonymous> (tests/queue.test.ts:28:29)
ts-jest[config] (WARN) [94mmessage[0m[90m TS151002: [0mUsing hybrid module kind (Node16/18/Next) is only supported in "isolatedModules: true". Please set "isolatedModules: true" in your tsconfig.json. To disable this message, you can set "diagnostics.ignoreCodes" to include 151002 in your ts-jest config. See more at https://kulshekhar.github.io/ts-jest/docs/getting-started/options/diagnostics
PASS tests/timeout.test.ts
Test Suites: 1 failed, 1 passed, 2 total
Tests: 1 failed, 21 passed, 22 total
Snapshots: 0 total
Time: 8.519 s
Ran all test suites.
Note for next cycle: This failed due to test assertion failures. Read the failing test carefully — if the logic is fixable, fix it. Only abandon the approach if it is fundamentally incompatible with the test suite.