Record time measurements in microseconds
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go
- Domain
- backend, observability
Research direction
Start by locating the timing measurement code used by RPC methods such as newPayload, then inspect how durations are currently recorded and which unit they use. Done means fast RPC calls are reported with microsecond precision, with existing measurement behavior checked for relevant methods.
Written by the indexing model from the issue text.
Description
Some RPC methods like newPayload complete in under a few milliseconds, so having greater precision for these methods would be great
- Dominant language
- Go
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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.
More from flashbots/bproxy
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in flashbots/bproxy
Similar issues
-
area/dev-productivity area/disaster-recovery area/ipcei kind/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
kind/bug status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
🤔 refinement needed
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
equinor/radix-operator#1979 ·