rust-windowing / rust-windowing/winit
Profile and benchmark performance of winit event handling
Open
Nobody has claimed this yet.
H - help wanted
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 1.3k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 9
Description
Over at Bevy, we're seeing some non-trivial hiccups based on how many inputs must be handled: https://github.com/bevyengine/bevy/issues/4691
To the extent possible, it would be good to profile and optimize the event handling done by winit.
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 reviewing the linked Bevy issue and profiling winit's event handling under the input load described there. Record a baseline and identify a measurable optimization target; done means a documented benchmark or profile and an agreed improvement, with regression coverage where applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100