TheAngryByrd / TheAngryByrd/MrBuild
Measure Coordinator-boundary F# editor latency
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Part of #19
Question
What is the editor-visible latency and resource profile of the current F# Project Mode path at the real Coordinator/Worker stdio boundary?
Measure, on the same corpus where practical:
- cold Coordinator process startup through initialization, workspace selection, first snapshot, first F# diagnostic;
- warm snapshot reload/project load and first diagnostic;
- range-based document edit to diagnostic publication;
- saved source-order and project-reference dependent refresh;
- overlapping versioned requests,
MaxConcurrentAnalyses, andDiscardedResults.
Separate process startup, Project Worker Design-Time Evaluation, Worker RPC, FCS analysis, and response publication so the direct FCS baseline can be compared with end-to-end editor cost.
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 at the current F# Project Mode Coordinator/Worker stdio path and use the same corpus where practical. Measure cold and warm flows, edits, dependent refreshes, and overlapping versioned requests, separating startup, design-time evaluation, Worker RPC, FCS analysis, and response publication. Done means a resource and latency report compared with the direct FCS baseline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100