tests: add simple storage performance tests #649
Conversation
marmarek
force-pushed
the
storage-perf
branch
from
8470828 to
129be05
Compare
marmarek
force-pushed
the
storage-perf
branch
from
129be05 to
664c5dd
Compare
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025021317-4.3&flavor=pull-requests Test run included the following:
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025020404-4.3&flavor=update
Failed tests86 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/127852#dependencies 30 fixed
Unstable testsPerformance TestsPerformance degradation:No issues Remaining performance tests:52 tests
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #649 +/- ##
==========================================
- Coverage 69.71% 69.69% -0.02%
==========================================
Files 58 58
Lines 12499 12511 +12
==========================================
+ Hits 8714 8720 +6
- Misses 3785 3791 +6
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
Aims to iterate in goal of fixing QubesOS/qubes-issues#7300 |
Add few simple storage performance tests using fio tool. Tests are checking dom0's root and varlibqubes pools (by default the same thing, but in case of XFS or BTRFS setups, they are different). And VM's root/private/volatile. The last one is tested by creating ext4 filesystem there first. This isn't very representative (normally volatile is used for swap and CoW data), but allows comparing results with other volumes. The tests can be also started outside of the full test run by calling /usr/lib/qubes/tests/storage_perf.py. It requires giving name of a VM to test (which may be dom0). The test scenarios are modeled after what kdiskmark tool uses. QubesOS/qubes-issues#5740
marmarek
force-pushed
the
storage-perf
branch
from
664c5dd to
6bcfcc8
Compare
Add few simple storage performance tests using fio tool. Tests are checking
dom0's root and varlibqubes pools (by default the same thing, but in case
of XFS or BTRFS setups, they are different). And VM's
root/private/volatile. The last one is tested by creating ext4 filesystem
there first. This isn't very representative
(normally volatile is used for swap and CoW data), but allows comparing
results with other volumes.
The tests can be also started outside of the full test run by calling
/usr/lib/qubes/tests/storage_perf.py. It requires giving name of a VM to
test (which may be dom0).
QubesOS/qubes-issues#5740
This PR is on top of #647