ValveSoftware / ValveSoftware/Proton
fsync performance results
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32.8k
- Forks
- 1.6k
- PR merge metrics
- PR metrics pending
Description
Post your performance results here! If they're a regression, please also report them in the dedicated fsync issue https://github.com/ValveSoftware/Proton/issues/2922.
Make sure you're running the same build of Proton 4.11 on both sides (eg. don't compare 4.2 with 4.11), and the only difference is fsync toggled on or off. (PROTON_NO_FSYNC=1 vs. not)
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
Use the same Proton 4.11 build for both runs, changing only PROTON_NO_FSYNC=1 versus fsync enabled. Compare the performance results and post them here; report any regression in the dedicated fsync issue, ValveSoftware/Proton#2922.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 20/100