dotnet / dotnet/performance

Monthly Performance Report Feedback/TODO

Open
#2,412 2 comments 1 reaction 3 assignees Claimed by @jeffhandley View on GitHub
Dominant language
F#
Stars
773
Forks
301
Avg merge
6d 9h
Merged PRs (30d)
15

Description

Here is a TODO list for next month, based on open discussions and user feedback. Will be updated as more feedback comes in.
- [ ] Discuss testing of nativeaot, clarify in instructions which users are responsible for running this
- [x] Clarify that two previews can still be run back to back if the resume feature is not wanted
- [x] Add a row for ubuntu 22.X to the table
- [ ] Add automatic architecture detection to the instructions once we agree on the robustness of the feature
- [ ] Debug preview 4 "arm" architecture problem
- [ ] Multiple users reporting crashing/hanging during Perf.FileStream.cs benchmarks (like FlushAsync). One using WSL, one using windows 11.
- [ ] Crashing/hanging also being reported for other async tests, like System.IO.Tests.Perf_RandomAccess.ReadAsync(fileSize: 1048576, bufferSize: 4096, options: None)
- [ ] Attempting to resume after one of the above crashes not working (see email from Andy Ayers with specifics)
- [ ] "instructions nit -- why is --architecture required on Linux? there is no "WOW64" layer like in Windows that I know of, so it should just pick up the architecture of the machine."
- [ ] Add explicit reminder to tell users to make sure their computer stays on during the runs
- [ ] Add explicit reminder to run terminal with sudo

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.