Compare PyGhidra and GhidraMCP performance
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 440
- Forks
- 48
- Avg merge
- 28m
- Merged PRs (30d)
- 1
Description
The PyGhidra backend is being built out, create a harness for testing the PyGhidra v.s. GhidraMCP timing for how long prompts/requests take
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the PyGhidra backend and the GhidraMCP request paths, then determine how prompts and requests are currently issued. Build a repeatable harness that measures their timing and makes the two backends comparable. Done means the same workload can be run against both and produces usable timing results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, reverse-engineering, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100