humanmade / humanmade/aws-xray
Collect memory information alongside stack
- Dominant language
- PHP
- Stars
- 29
- Forks
- 3
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 1
Description
Currently, we collect just what the current function stack is at each tick. In order to aid memory debugging, we should also collect memory usage at each tick.
This would help immensely with understanding when memory is actually used, as it's rarely the case that this is actually at the memory error location.
See also:
* https://phabricator.wikimedia.org/T399210
* https://github.com/arnaud-lb/php-memory-profiler
Contributor guide
No contributing guide indexed for this repository
Research direction
No file or test is named. Start by tracing the existing code that collects the current function stack at each tick, then review the linked PHP memory profiler for relevant memory measurements. Done means memory usage is collected alongside the stack for every tick.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, php
- Domain
- backend, observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100