josdejong/workerpool

Performance profiling of workers

Open

#512 opened on Aug 25, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (164 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (2,307 stars)
PR merge metrics
 (Avg merge 21d 16h) (3 merged PRs in 30d)

Description

When profiling the performance of web workers orchestrated by workerpool in Chrome Dev Tools, the actual code tree being executed in the worker seems to be masked away (see yellow Function Call blocks in the screenshot). Is there a way to profile and get the performance measurements of what exactly runs inside the worker? Thanks

Contributor guide

Research direction
Investigate why Chrome DevTools shows 'Function Call' instead of actual function names for workerpool workers. Check if source maps are properly loaded or if the worker code is wrapped in a way that hides the original code. Consider adding custom profiling markers using console.profile or performance.mark.
Tech stack
javascript
Domain
performance
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75