Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Research Universities edition of October 25, 2026

Vendor claimEmergingNew this fortnight

University of Leeds Calder HPC first week (21 Oct): over 156,000 jobs, 90.3% average GPU utilisation on NVIDIA H200 NVL nodes and 82.2% peak utilisation, while proprietary applications and Slurm tuning are still catching up

University of Leeds Research Computing (Advanced Research Computing) · University research computing · Leeds, United Kingdom (transferable to U.S. university research computing centres)

Publisher
University of Leeds Advanced Research Computing
Original publication
21 October 2026 (ARC Leeds news post)
Source retrieved
2026-10-26
Event date
2026-10-09
Read original source

What happened

The University of Leeds research computing team reports that in Calder's first seven days of service, researchers submitted over 156,000 jobs across a range of disciplines; GPU utilisation averaged 90.3% over the week and thousands of CPU jobs drove peak utilisation to 82.2%. Two researchers describe early use: a 3D scene-understanding group submitted over 2,700 CPU and 500 GPU jobs and said the H200 GPUs' large memory let them run big 3D models on whole scenes, and an Earth-sciences postdoc said the H200 NVL GPUs considerably sped up training of physics-informed neural networks. The team says the familiar setup carried over from the existing Aire cluster, but several applications, particularly proprietary software, are not yet available on Calder, users depending on them are asked to stay on Aire, and the team is still refining Slurm for growing and diverse workloads. The 9 October launch post says Calder was procured through an academic-led process approved by the Research IT Steering Group (MTI with Dell hardware, support from Cambridge Research Computing), with security checks and user testing before launch.

Why it matters

A rare early operating metric for a new university AI and HPC cluster. It shows demand for GPU capacity can saturate a new system within a week, and that software availability and scheduler tuning lag hardware, useful benchmarks for U.S. research computing centres planning launches and capacity.

Evidence and measured results

Read the full 21 Oct 2026 ARC Leeds post (datePublished in page metadata): 156,000+ jobs in seven days, 90.3% average GPU utilisation, 82.2% peak utilisation, two named researcher testimonials, proprietary software gap and Slurm refinement. Opened the 9 Oct 2026 launch post for procurement (Research IT Steering Group, MTI, Dell, Cambridge Research Computing) and pre-launch security checks and user testing.

Limitations and uncertainty

Self-reported by the operating team in a promotional post; no definitions of utilisation, queue wait data, user counts, GPU counts or baseline comparison with Aire are given. One week of data, likely affected by launch-period backlog migration. Testimonials are selected by the operator. GPU model and counts beyond "H200 NVL" are not stated in the inspected posts.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-25; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
Universities launching new GPU clusters face immediate demand saturation while software availability and scheduling policy lag.
Stakeholders
  • Research computing director
  • CIO
  • Research IT steering group
  • Heavy GPU research groups
Discovery questions
  • Which applications must be ready on day one?
  • How will GPU time be allocated when demand exceeds supply?
  • What utilisation and wait metrics will you report?
Value hypothesis
Launch-readiness planning may shorten the period in which users must stay on legacy systems and make GPU allocation transparent.
Potential engagement
A launch-readiness review covering application porting, licensing, scheduler policy and metrics for one planned cluster.
Unsupported claims
  • Sustained 90% GPU utilisation
  • Research productivity gains
  • Return on investment

Pre-sales engineering

Role takeaway
Fit
Fits universities adding GPU capacity alongside an existing HPC system.
Architecture and integration
CPU and H200 NVL GPU partitions under Slurm, run in parallel with a legacy cluster and a consistent user environment.
Prerequisites
  • Application porting and licences
  • Scheduler and fair-share design
  • Monitoring of utilisation and waits
Constraints
  • One week of operator data
  • No queue or user metrics
  • Proprietary software lag
Security
Complete security checks before launch and keep consistent access controls across old and new clusters.
Proof of value
  • Define and report utilisation and queue waits
  • Track application availability against plan
  • Compare job throughput with legacy cluster

Delivery

Role takeaway
Work
Port and license applications, configure scheduling, run parallel service, collect metrics and gather user feedback.
Dependencies
  • Software vendor licences
  • Integrator support
  • Researcher user testing
Ownership
Research computing service, governed by a research IT steering group.
Skills and adoption
Keep the user environment consistent to limit retraining; train staff on scheduler tuning for mixed workloads.
Governance checkpoints
  • Pre-launch security and user testing sign-off
  • Scheduler policy review after first month
  • Legacy cluster retirement decision
Acceptance criteria
  • Proposed: priority applications available by an agreed date
  • Proposed: published queue-wait metric by partition
  • Proposed: defined utilisation measure reported monthly
Risks
  • GPU saturation causing long waits
  • Licensing delays
  • Unclear metrics overstating success

Implementation considerations

Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.

Architecture and integration

What must connect, and where does the AI sit in the workflow?

Hybrid CPU and NVIDIA H200 NVL GPU cluster run alongside an existing system (Aire) under Slurm; keeping the user environment consistent with the previous cluster eased migration.

Governance

Who approves, reviews and stays accountable for outcomes?

Academic-led procurement via a Research IT Steering Group; capacity allocation and fair-share policies will matter as GPU demand stays near saturation.

Security and privacy

What data, permissions and controls need testing?

Security checks were completed before launch; no further detail is given.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Familiar environment reduced onboarding effort; behind-the-scenes infrastructure staff effort is emphasised but not quantified.

Procurement

What should contracts, pricing and exit terms secure?

Academic-led tender with an integrator and external support partner; software licensing (proprietary applications) lagged hardware readiness.

Operating model

Which teams own the service once it runs?

Running new and legacy clusters in parallel during migration, with community feedback channels and continuous scheduler tuning, is the stated operating approach.

Publication history

  1. 2026-10-25Research Universities · Issue 474 resources
Read preserved resource versions (JSON)

Stable resource ID: leeds-calder-hpc-first-week-156k-jobs-90-percent-gpu-utilisation-20261021