Evaluate GCE VMs as an execution environment for performance-sensitive scanning
Open
Nobody has claimed this yet.
hackbot
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
Description
Spike to assess whether full-control VMs (GCE) are needed for performance-scanning agents, where Cloud Run's constraints (no host-level perf counters, cold start variance) may be limiting.
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
The issue mentions Cloud Run constraints and GCE VMs but names no files, tests, or entry points. Start by locating the performance-scanning agents and their current execution environment, then define the evaluation criteria and document whether GCE addresses host-level perf-counter access and cold-start variance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, python
- Domain
- cloud, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100