microsoft / microsoft/tolerant-php-parser
CPU profiling to identify potential performance improvements
Open
Nobody has claimed this yet.
discuss
performance
- Dominant language
- PHP
- Stars
- 894
- Forks
- 85
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
Also any suggestions for tools? There's xdebug + webgrind... any other favorite workflows?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by profiling the PHP parser with the mentioned Xdebug and webgrind workflow, then compare other profiling tools or workflows. Done means documenting useful profiling options and identifying potential performance improvements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100