Skip to content

Comments

Use QueueDepth in diskspd MetricScenario#645

Merged
V-ManuelRM merged 1 commit intomainfrom
users/v-manuelrod/diskspd-visual-bug-fix
Feb 20, 2026
Merged

Use QueueDepth in diskspd MetricScenario#645
V-ManuelRM merged 1 commit intomainfrom
users/v-manuelrod/diskspd-visual-bug-fix

Conversation

@V-ManuelRM
Copy link
Contributor

Changed incorrect ThreadCount -> QueueDepth parameter on MetricScenario name for DISKSPD profile

Changed incorrect ThreadCount -> QueueDepth parameter on MetricScenario name for DISKSPD profile
Copy link

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 fixes a bug in the DISKSPD profile where the MetricScenario name incorrectly used d{ThreadCount} instead of d{QueueDepth} for the RandomWrite_4k_BlockSize scenario. The 'd' prefix in the naming convention represents queue depth, not thread count, as consistently used across all other scenarios in DISKSPD and FIO profiles.

Changes:

  • Corrected MetricScenario parameter from d{ThreadCount} to d{QueueDepth} in RandomWrite_4k_BlockSize scenario

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@V-ManuelRM V-ManuelRM enabled auto-merge (squash) February 20, 2026 00:03
@V-ManuelRM V-ManuelRM merged commit 4f35e59 into main Feb 20, 2026
10 checks passed
@V-ManuelRM V-ManuelRM deleted the users/v-manuelrod/diskspd-visual-bug-fix branch February 20, 2026 00:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants