# VAST Data solves job-level noisy neighbor problem

> Source: <https://www.blocksandfiles.com/flash/2026/11/18/vast-data-solves-job-level-noisy-neighbor-problem/5310759>
> Published: 2026-11-18 14:19:00+00:00

**Key takeaway:** VAST AI OS 5.6 will let administrators set independent per-job bandwidth and IOPS policies via job identifiers carried in VAST NFS 4.8 client requests, adjustable in real time without restarting jobs, with telemetry through the open-source VNFS Collector into Prometheus, Grafana or the VAST DataBase

FLASH

# VAST Data solves job-level noisy neighbor problem

[VAST Data](https://www.blocksandfiles.com/flash/2026/11/05/vast-data-gets-vast-increase-in-orders-for-its-all-flash-storage/5307771) has made job level bandwidth and IOPS levels controllable so that longer-running jobs aren’t slowed by other jobs hogging bandwidth or IOPS.

The company says that administrators of large-scale computing environments have faced a familiar problem: a single I/O-intensive job can slow down dozens of others, with few options to intervene without disrupting ongoing work. On the world’s largest computing systems, a critical simulation can be delayed by an unrelated analysis workload, even when ample computing power is available. For research institutions and AI infrastructure providers, this competition creates unpredictable performance, operational disruption, and inefficient use of expensive infrastructure.

Glenn Lockwood, Principal Technical Strategist at VAST Data, said: “Anyone who's used a supercomputer knows the frustration of unpredictable performance when another job consumes more than its share of shared resources. The scheduler knows exactly which jobs are running, but that understanding has historically stopped at the storage system. With Job-Level QoS, we’re closing that gap. The storage system itself can now manage the I/O performance it delivers to individual jobs competing for resources, allowing resource managers and schedulers to prioritize bandwidth and IOPS without having to cancel jobs or change how applications run.”

Job-Level QoS extends the job identity defined by workload managers such as [Slurm](https://slurm.schedmd.com/overview.html), PBS Pro, and LSF into the VAST data layer. This allows organizations to treat I/O performance as an allocatable resource alongside compute, enforcing individual bandwidth and IOPS policies on a job-by-job basis and adjusting allocations in real time while workloads continue running. Administrators can protect priority workloads and make more productive use of shared infrastructure without interrupting the research and applications depending on it.

VAST AI OS has several new controls to enable this:

- Enforce QoS at the individual job level: The VAST NFS client carries configurable job identifiers with I/O requests, enabling VAST to apply independent bandwidth and IOPS policies to multiple jobs sharing a single compute node, or manage the collective I/O of a job spanning multiple nodes under a single policy.
- Adjust performance without interruption: Administrators can modify read and write performance policies in real time, without restarting jobs, modifying applications, or remounting storage.
- See which jobs are consuming resources: The optional, open-source VNFS Collector provides job-level visibility into bandwidth, IOPS, and errors, with telemetry available through Prometheus, Grafana, or the VAST DataBase.
- Extend controls beyond batch: The underlying architecture also supports Kubernetes and other orchestrators, enabling workload-level performance management across AI training, inference, and scientific computing environments.

VAST will demonstrate Job-Level QoS in action at [SC26](https://sc26.supercomputing.org/),  showing how administrators can identify competing jobs, dynamically adjust bandwidth allocations, and enforce independent performance policies across shared infrastructure while workloads continue running uninterrupted.

Job-Level QoS is planned for general availability with VAST AI OS 5.6 in late January or early February 2027, requiring VAST NFS 4.8 or later.
