CPU profiling to identify potential performance improvements

Open
#15 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
performance

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.

Description

discuss performance

Also any suggestions for tools? There's xdebug + webgrind... any other favorite workflows?

Dominant language
PHP
Stars
894
Forks
85
Avg merge
2d 13h
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/tolerant-php-parser

All issues in microsoft/tolerant-php-parser

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.