Minutes
We were able to release
WindowsPerfv1.0.0 in December 2022, see release 1.0 in JIRA.We also released follow up version
1.0.1which is a minor release intended to imrove on Jira output feature, see !67.
Sprint 6 was the longest one till now. Main goal achhieved during last sprint were:
Add JSON feature to
wperf. This will allow third party applications to executewperfand parse results in convenient, standarised way.We now have simple Python test script which we can use to test
wperfapplication againswperf-driver. Test script is using simple PyTest testcases to check ifpwerfoutput matches requirements. See wperf_cli_test.py.
First 1-2 weeks on January are usually busy and developers are wrapping up other things.
We are with sprint 7 restarting work on WindowsPerf.
Work with JIRA:
Improvement: all developers should update tickets when their status changes to e.g. in progress or close.
Improvement: all developers should include links to GitLab issues and merge requests related to tickets open in JIRA. This is important as it serves bridge between what we do and where to find it. It’s also a proof which is desired during development.
Pledge: This year we will focus on (in addition to curent tasks)
Merging and improving Sampling Model - working, but not yet ported version was implemented and presented to the team by Jiong Wang (Deactivated) in December 2022.
Testing and CI/CD.
Investigate if we can have Pipeline with x86 → ARM64 build as a sanity check
Improve testing: both unit test and functional testing for WindowsPeprf project.
When we write code, especially in
wperfnow we can add unit tests inwperf-testproject or add functional tests to wperf_cli_test.py.
Sign WindowsPerf Windows driver. We need to:
Make sure we can release WindowsPerf as a tool developers can use (as intended):
We want users to use
WindowsPerfthe same way Linux users useperf.We want hassle free Windows Kernel Driver installation (
wperf-driver).We want users to use WindowsPerf on their machines without need to disable e.g. SecureBoot.