Skip to content

Commit bb9a418

Browse files
committed
update node,js heap readme
1 parent e4667cf commit bb9a418

1 file changed

Lines changed: 1 addition & 10 deletions

File tree

scenarios/node_heap/README.md

Lines changed: 1 addition & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -14,17 +14,8 @@ Both functions are called once per iteration in a timed loop, creating equal **n
1414

1515
**Objects Profile**: Should count allocation instances
1616
- Theoretically: 50% `a` / 50% `b` (equal number of calls)
17-
- Actually measured: 33% `a` / 66% `b` (biased toward larger objects)
17+
- Measured: Matches expectations
1818

1919
**Space Profile**: Should count memory usage
2020
- Expected: 33% `a` / 66% `b` (proportional to allocation sizes)
2121
- Measured: Matches expectations
22-
23-
## Open Questions
24-
25-
The objects profile shows bias toward larger allocations (66% vs 50% expected), suggesting the Node.js heap profiler may be:
26-
- Sampling based on allocation size rather than allocation count
27-
- Using size-weighted sampling for performance reasons
28-
- Exhibiting V8 engine optimization effects on string allocation
29-
30-
**TODO**: Clarify with the Node.js profiler team how sampling works and why there's bias toward larger objects in the objects profile.

0 commit comments

Comments
 (0)