Skip to content

Conversation

@syeleti-msft
Copy link
Member

@syeleti-msft syeleti-msft commented Jul 28, 2025

Type of Change

  • Bug fix
  • New feature
  • Code quality improvement
  • Other (describe): Add FIO workloads

Description

  • Feature / Bug Fix: (Brief description of the feature or issue being addressed)
    ** 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.

Copy link
Contributor

Copilot AI left a 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

@vibhansa-msft vibhansa-msft modified the milestones: v2-2.6.0, v2-2.5.1 Jul 29, 2025
@vibhansa-msft vibhansa-msft merged commit 43314da into main Sep 29, 2025
11 checks passed
@vibhansa-msft vibhansa-msft deleted the syeleti/fio-tests branch September 29, 2025 10:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants