PowerEdge: Performance Issues on Linux Hosts when PERC or HBA Controllers use NVMe or SSD

Summary: Linux host reports reduced storage performance when using PERC or HBA controllers with attached SSD or NVMe devices.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

Systems running Linux exhibit lower‑than‑expected performance on SSD or NVMe drives connected through PERC or HBA controllers. Symptoms include reduced IOPS, elevated latency, or suboptimal throughput relative to expected device or platform capabilities.

Cause

Modern PERC RAID and HBA controllers present attached storage devices to the OS through a SCSI device model, even when the underlying media is NVMe. Because these devices appear as SCSI SAS targets, most Linux distributions automatically apply legacy block‑I/O scheduling policies optimized for rotational hard drives. When SSD or NVMe devices are forced through these HDD‑oriented schedulers, the result can be reduced throughput and higher latency compared to their native performance.

Relevant Controller Models

  • PERC: H740P, H840, H745, H345
  • PERC: H750, H755, H350, H355
  • PERC: H965, H365
  • PERC: H975
  • HBA345
  • HBA355
  • HBA465

Resolution

Refer to your Operating System storage optimization guide. Linux OS typically sets the scheduler for Native NVMe configurations to "none."

Red Hat Enterprise Linux 8 and 9 "Setting the disk scheduler" guides:

SLES 15-SP6 "Tuning I/O performance" guide:

For SSD and NVMe attached PERC and HBA configurations, changing the block scheduler to "none" may show improved performance.

To check the current scheduler:
As superuser, run cat /sys/block/{SD}/queue/scheduler where {SD} is the device block entry under /dev (example sda)

Screenshot showing a scheduler set to mq-deadline in Red Hat Enterprise Linux 9 for sda

scheduler

To check the current scheduler:
As superuser, run, echo "none" > /sys/block/{SD}/queue/scheduler where {SD} is the device block entry under /dev (example sda)

Screenshot showing the scheduler being updated to "none" for sda

scheduler  "none"

 

Note: The above change is not persistent across reboots and does not follow the drive or VD if the /dev block device name changes. A UDEV rule can be added for the device WWID to persistently change the scheduler to "none." Refer to your OS user guide for instructions on creating UDEV rules or similar mechanisms for setting block device parameters.

Additional OS settings tweaks and power profiles changes may be required to achieve maximum controller and drive performance. Refer to any OS performance tuning and BIOS power profile documentation.

Affected Products

HBA345, HBA350i, HBA355, Host Bus Adapter HBA465e Adapter, Host Bus Adapter HBA465i Adapter, Host Bus Adapter HBA465i Front, PowerEdge RAID Controller H350 Adapter SAS, PowerEdge RAID Controller H355 Front SAS , PowerEdge RAID Controller H355 Adapter SAS, PowerEdge RAID Controller H365i Adapter, PowerEdge RAID Controller H365i Front DC-MHS, PowerEdge RAID Controller H745, PowerEdge RAID Controller H745P MX, PowerEdge RAID Controller H750 Adapter SAS, PowerEdge RAID Controller H755 Adapter, PowerEdge RAID Controller H755 MX Adapter, PowerEdge RAID Controller H755N Front NVMe, PowerEdge RAID Controller H755 Front SAS, PowerEdge RAID Controller H965i Adapter, PowerEdge RAID Controller H965i Front, PowerEdge RAID Controller H965i MX, PowerEdge RAID Controller H975i Front, PowerEdge RAID Controller H740P, PowerEdge RAID Controller H840, PowerEdge RAID Controller H965e Adapter ...
Article Properties
Article Number: 000458506
Article Type: Solution
Last Modified: 29 مايو 2026
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.