-
Couldn't load subscription status.
- Fork 239
Add FIO tests to check the data integrity #1893
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds FIO (Flexible I/O tester) workloads to test data integrity for file cache and block cache in Blobfuse2. The tests are configured as an optional stage that doesn't run by default.
- Introduces comprehensive FIO test configurations for various I/O patterns including sequential, random, and hole-based workloads
- Adds a new pipeline stage for running FIO tests with both file cache and block cache configurations
- Increases file cache size limit from 2GB to ~20GB to accommodate larger test workloads
Reviewed Changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| testdata/config/azure_key.yaml | Increases max-size-mb for file cache from 2048 to 20480 |
| test/fio/*.fio | Adds FIO job configuration files for different test scenarios |
| blobfuse2-nightly.yaml | Adds optional FIO test stage to nightly pipeline |
| azure-pipeline-templates/fio-data-integrity.yml | Implements FIO test execution template |
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Type of Change
Description
** Add fio workloads to check the data integrity of the file cache and block cache.
** Making the stage not run by default due to the known issues.