StacklokLabs / StacklokLabs/yardstick
Implement Caller-Specified Response Delay in Yardstick
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4
- Forks
- 2
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 7
Description
We want to run performance tests through the ToolHive proxy. However, because Yardstick simply echoes back a response, there are no external network calls, resulting in the fastest possible response times. To better simulate real-world conditions, we should add a configurable delay mechanism that callers can specify and that Yardstick will honour by waiting a defined amount of time before responding. This would more accurately model a production MCP server, which may take several seconds to return a response.
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
Start by locating Yardstick's MCP request and response entry point and determine how callers could provide a response delay. Confirm the expected delay behavior for requests sent through the ToolHive proxy, then verify that Yardstick waits for the requested duration before responding without changing requests that omit it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100